docs: add guide about debugging Playwright Python #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently its hard to debug Playwright Pytest tests on bots when they are failing until screencast is not ready. Many users in the Jest world use such a feature for debugging the tests or getting insights why something is not working when they are failing on the bots.
This implementation is opt-in and will create a screenshot when a test is failing, in the future we can add a screencast recording for each test in the folder too.
Blocked by upstream: microsoft/playwright-python#166
I think we could also add a
--breakpoint-on-error
flag e.g. which will start a REPL once a test is failing. Also opt-in. Then the user can interact with the browser via the headful instance or via the REPL.