Playwright - test execution is stuck if there is a version mismatch
anupamck opened this issue · 1 comments
The symptom: My CI execution pipeline is stuck on the following step:
...
npm timing npm:load:timers Completed in 0ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load Completed in 64ms
Running 4 tests using 4 workers
I notice that moon pods for the execution are created in my infrastructure, but they are killed almost immediately, and the pipeline remains stuck on this step forever.
I found out that this was due to a version mismatch between the Playwright package I use to locally write the tests (and deploy as a package for execution), and the Moon Playwright image I use for the run (which I pick from here: https://aerokube.com/images/latest/#_playwright).
This is expected - I need these versions to match for my tests to run smoothly. But what I expect here is better error handling on Moon. Once a version mismatch is detected, I expect the pipeline to throw an error with a descriptive error message.
@anupamck we unfortunately have no control on Playwright error handling, because their protocol is not a W3C standard like Selenium protocol is. So, I would create an issue in Playwright repository instead.