Add Replay to the Playwright test suite #53298
Conversation
|
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @jaril! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
|
Heads up @kevin940726 🙋♂️ |
|
@WunderBart, @kevin940726, I think this would have been super handy with some recent flaky tests, that turned out to be actual bugs. |
|
We already have the native Playwright Trace which seems to cover the same functionality. What would be the reason to use Replay over this? |
|
Thanks for contributing, @jaril! I'm going to close this PR as stale. The native traces seem to be just good enough for the project. |
What?
This adds the Replay Playwright integration, so that we generate recordings of the playwright test suite.
Why?
These recordings (for example, avatar.spec.js) make it easier to debug test failures with time-travel debugging. Here's a quick demo of what this debugging workflow looks like in practice.
How?
Run CI with the PR. Replays are automatically recorded while the test suite runs, and are uploaded with
replayio/action-upload. The logs of that step will contain the links to the uploaded replays.To access them more conveniently on a per-run basis, you can join the gutenberg CI team in replay using this link.
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast
https://www.loom.com/share/e0c85acce6ce4d029704e7b8bea7720b