Bug Replay & Test Recorder
Keep a reproducible sequence.
Record a supported test path, replay it and inspect where it fails.
Keep a reproducible sequence.
When reproducing a bug or checking an earlier scenario again.
A description such as “the button failed” leaves important steps unstated. Recording a supported test sequence gives you actions and results you can revisit.
Record a scenario, inspect its steps and replay it against the appropriate local runtime. Keep failed and successful evidence distinct.
How to get started.
From your first choice to the result. Here is how to use this feature in your own project.
- 01
Start recording in a supported local test runtime and perform the scenario.
- 02
Save the recording and replay the captured actions.
- 03
Inspect steps, available images, output and source information to guide a fix or regression test.
How it could work for you.
Record opening a collection, navigating to contact and checking a required field.
How to assess the result
Not every browser action or environment is supported. A replay result applies to the tested scenario and version.
Where to find it.
Top bar → Tools → Bug Replay & Test Recorder
Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.What is saved?
Recordings, replay results and available evidence files are retained as test history.
What you need to know
Recording and replay require a suitable local runtime. A successful scenario does not test the entire application.