Definition
The trace viewer is the detailed investigation page that combines test steps, screenshots, browser video, timeline events, network requests, and console messages.
What it is for
It lets you reconstruct exactly what happened during a run without repeating it.
How it works
- The viewer combines the run’s steps, screenshots, browser video, timeline events, network requests, and console messages in one page.
- Filter to one test in a multi-test run, search console messages, and filter network requests by all, failed, XHR, or documents.
- A filmstrip and video let you scrub through what the browser actually displayed.
Example
A checkout test fails. The trace shows the click, the browser video, a 500 network response, and the matching console error at the same time.
Common use cases
- Debug a failed step.
- Inspect a slow request.
- Review browser console errors.
- Watch the recorded run video.
Where to find it
Open a run and select Trace. Use the Overview, Timeline, Console, Network, and other tabs.
Limitations, requirements, and permissions
- Some views need captured artifacts; the filmstrip or video may be unavailable when they were not recorded.
- Requires access to the run and its trace artifact.
Related features and guides
Ready to try it yourself?
Create your free account, record your first flow, add a validation, and let Rima run it on a schedule for you.
Start free trial