Replay is a new debugger for recording and replaying software. Debugging with Replay should be as simple as viewing print statements and more powerful than pausing with breakpoints. Of course, debugging should be collaborative as well!
Feel free to file any issues you see while recording or replaying.
We track feature requests in Canny. We use Canny for 3 reasons:
- To discuss the future of Replay with the community
- To plan in the open. Our roadmap is transparent :)
- To keep the issue backlog actionable.
Replay's DevTools is a React app built on top of the Replay protocol. Getting started is as simple as:
git clone git@github.com:RecordReplay/devtools.git
cd devtools
npm install
npm start
Once you see Compiled succesfully
in your terminal, open your browser and go to this link.
You just successfully opened your first Replay recording! That recording uses your locally running copy of Replay DevTools to debug our test recording.
You can now debug recordings, but you can't make them. Yet.
To get started with recordings, say hi to us on Slack đź‘‹ and request recording instructions. We're happy to get you set up with a recording account from there!
Everybody's welcome to join us on Slack. We can help with getting started with the project, finding issues to work on and chatting about the future of DevTools.
node test/run.js [--pattern pat]
If you want to run the tests against a local build of the browser, you'll need to invoke the tests like so:
RECORD_REPLAY_PATH=~/devel/gecko-dev/rr-opt/dist/Replay.app RECORD_REPLAY_BUILD_PATH=~/devel/gecko-dev node test/run.js
Replace the paths with the appropriate paths to and within gecko-dev
as appropriate in your environment.
If you want to run the tests against a local build of the backend, you'll need to invoke the tests like so:
RECORD_REPLAY_SERVER=ws://localhost:8000 RECORD_REPLAY_DRIVER=~/devel/backend/out/macOS-recordreplay.so node test/run.js
Replace the paths with the appropriate paths within the backend
repo as appropriate in your environment.