Error when attempting to run tests via pac cli on msedge browser
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp, playwright
- Domain
- cli, testing-qa
Research direction
Reproduce the failure with sample/buttonclicker/testRun.fx.yaml and testSettings.yaml using pac test run with channel: msedge. Start with PlaywrightTestInfraFunctions.SetupAsync in the stack trace and compare it with the successful run without the channel setting. Done means the Button Clicker test cases launch Edge and run successfully.
Written by the indexing model from the issue text.
Description
- Please attach the test suite YAML & .msapp which demonstrates the issue you are experiencing and any logs written to the specified outputDirectory. (Please do not attach any file which may contain sensitive personal or company data.)
Describe the bug
Error when launching Edge browser with Button Clicker Sample test YAML
To Reproduce
Steps to reproduce the behavior:
- open sample\buttonclicker
- run the
testRun.fx.yamlfile usingpac test runwithchannel: msedgeset in thetestSettings.yaml
Expected Behavior: test cases run and pass
Actual Behavior: received Playwright error when trying to open msedge browser:
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Playwright.Transport.Connection.d__401.MoveNext() in /_/src/Playwright/Transport/Connection.cs:line 206 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Playwright.Transport.Connection.<WrapApiCallAsync>d__521.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Playwright.Core.BrowserType.d__10.MoveNext() in /_/src/Playwright/Core/BrowserType.cs:line 56
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerApps.TestEngine.TestInfra.PlaywrightTestInfraFunctions.d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerApps.TestEngine.SingleTestRunner.d__29.MoveNext()
Additional context
Was able to get the test cases to run and pass when commenting out channel: msedge, as they ran on the chrome browser.
- Dominant language
- C#
- Stars
- 150
- Forks
- 55
- Avg merge
- 1h 18m
- Merged PRs (30d)
- 1
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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 2/5 1-3 hours Newbie friendliness 72/100
fluentassertions/fluentassertions#3353 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
unoplatform/uno#24769 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
AvaloniaUI/Avalonia#22323 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microsoft/onnxruntime-genai#2633 ·
Maintainers usually reply within 1 day