Replay helps the OSS community by making it easier for maintainers and contributors to debug user issues and automated test failures — all for free, support included.
Imagine if every new GitHub issue came with a recording of the code’s execution at the time the bug occurred with familiar debugging tools built in. That’s what you get with Replay.
- replay.io/record-bugs - a guide for end users that walks them through the recording process
- GitHub Issue template - encourage users to submit replays with this issue template
- Blog: Contributing to OSS with reproducible bug reports - how we used Replay to contribute to the open source Excalidraw project by debugging an open GitHub issue
Replay lets you upload source maps so recordings made from production applications are easier to debug. If you have any questions or a unique build process, we’ll walk you through the process.
Test failures can derail a pull request, whether it’s from a maintainer or a contributor. The Replay Playwright GitHub Action automatically generates replays of failed tests so you can quickly debug. It even posts the replays back to the pull request so you have all the context needed when reviewing PRs.
There are experimental versions of a Puppeteer and Cypress recorder, and we are working on supporting more CI providers.
Use Replay to clearly document changes made in a pull request — both to the code and application behavior. Add comments to lines of code explaining changes and specific areas of the UI. You can even add comments to network requests to highlight changes in requests or response bodies (experimental feature).