Launch Browser is failing after Switching to Edge Profile.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- authentication, testing-qa
Research direction
Reproduce the Basic Gallery run with the documented dotnet PowerAppsTestEngine.dll command and inspect the logs around the Edge profile switch. Trace the authentication failure and the subsequent provider access error. Done means MFA and profile switching complete successfully and the BasicGallery app is accessible in the browser.
Written by the indexing model from the issue text.
Description
Command used:
dotnet PowerAppsTestEngine.dll -u "storagestate" --provider "canvas" -a "none" -i "C:\PowerApps-TestEngine\samples\basicgallery\testPlan.fx.yaml" -t $tenantId -e $environmentId
Observed Behavior:
- The test suite Basic Gallery initiates successfully.
- Test results are directed to a temporary output folder.
- The Chromium browser launches and navigates to the expected app URL: https://apps.powerapps.com/play/e/9999999-aaaa-aaaa-bbbb-9999999e1f2ae/an/new_galleryapp_80360?tenantId=1111111-aaaa-aaaa-aaaa-aaaaa99999999&source=testengine
- The login process begins, including MFA authentication.
- A prompt appears to switch to the Edge profile.
- The switch process proceeds, but the launch fails at the authentication stage.
Error Messages:
Invalid login credential(s). For more details, check the logs.
[Critical Error] Could not access Provider. For more details, check the logs.
Test Summary:
Total test cases: 1
Passed: 0
Failed: 1
Expected Behavior:
Upon successful authentication and Edge profile switch, the BasicGallery app should launch and be accessible within the browser.
- 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
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
apache/arrow-adbc#4809 ·
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/vscode-azurefunctions#5197 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
microsoft/microsoft-ui-reactor#1274 ·