I was really tired with "Step In" and "Step Out" and "Step Over" since they have always killed time , it is always fortunate with trace option which allows you to go back to the previous Step while debugging and fixing the issue becomes very very easy.Thanks a lot for making our lives easier
You run your Playwright tests on CI, then upload a Trace after the tests completed and open the Trace locally on trace.playwright.dev. See here: playwright.dev/docs/ci-intro Usually you upload the playwright-report directory, which contains the full HTML report including the traces.
Such an underrated and too often overlooked useful tool.
I was really tired with "Step In" and "Step Out" and "Step Over" since they have always killed time , it is always fortunate with trace option which allows you to go back to the previous Step while debugging and fixing the issue becomes very very easy.Thanks a lot for making our lives easier
Thank you Debbie and Playwright team!
where is Slushnikov?
Yeah. Where is he?
How to open the trace viewer on CI? You missed the most important thing
npx playwright test --ui
You run your Playwright tests on CI, then upload a Trace after the tests completed and open the Trace locally on trace.playwright.dev. See here: playwright.dev/docs/ci-intro
Usually you upload the playwright-report directory, which contains the full HTML report including the traces.
thanks
How to add color pkg to your trace viewer?
Please file a bug report on GitHub if you have feedback on Trace Viewer, thanks!