Test run - timeout - never login
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- csharp
- Domain
- testing-qa
Research direction
Start with the supplied YAML test configuration and the test-engine login process, then review the logs showing “Desired url not found” and the recorded video. Trace why the configured user is set but the Next button is not passed; done means the login completes and the test case runs instead of timing out.
Written by the indexing model from the issue text.
Description
test file>
testSuite:
testSuiteName: Suite
testSuiteDescription: ''
persona: User1
appLogicalName: ""
appId: '26f78246-a4c0-4c27-990a-8f08278'
onTestCaseStart: ""
onTestCaseComplete: ""
onTestSuiteComplete: |
=
networkRequestMocks:
testCases:
- testCaseName: Case
testCaseDescription: ''
testSteps: |
=
SetProperty(TextInputrg.Text, "rg");
SetProperty(TextInputvm.Text, "rg");
SetProperty(TextInputobs.Text, "rg");
testSettings:
filePath:
browserConfigurations:
- browser: Chromium
device:
screenWidth: 1920
screenHeight: 1080
locale: en-US
recordVideo: true
headless: true
timeout: 30000
extensionModules:
enable: true
allowPowerFxNamespaces:
- Preview
environmentVariables:
filePath:
users:
- personaName: User1
emailKey: user1Email
passwordKey: user1Password
Describe the bug
Testing a canvas application using test-engine throws a timeout, and I've figured out using video record that never passes the login option, it sets the user configured, but never clicks on the next button
To Reproduce
Actual Behavior: tests never run, in logs appear: Desired url not found
in login process , sets user but never passes it
- Dominant language
- C#
- Stars
- 150
- Forks
- 55
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/PowerApps-TestEngine
-
new
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
new
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
new
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
question
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in microsoft/PowerApps-TestEngine
Similar issues
-
effort:S P3 refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1532 ·
-
core dependencies
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
C#/.NET Roslyn LSP Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
DotNetNext/SqlSugar#1458 ·