Open Traces

Open Playwright trace evidence from TestVibe to inspect actions, snapshots, timing, console, and network activity around a failure.

Playwright traces are detailed recordings of a test run. They can include actions, DOM snapshots, console events, network requests, timing, screenshots, and attachments.

Use traces when screenshots and videos show what happened but not why.

When traces are available

Trace availability depends on the run configuration. Many teams keep traces for failed tests so they can debug without storing large artifacts for every passed test.

Traces may be missing when:

Reason	What to check
Trace capture is disabled	Review the selected run configuration.
Trace is retained only on failure	Passed tests may not keep traces.
The run failed before Playwright ran	Check session setup and dependency installation.
The run is still finalizing	Wait for artifact processing to finish.
Artifacts expired or were deleted	Use a newer run or re-run the test.

Open a trace

1. Open Runs.

2. Select a completed or failed run.

3. Open the Features tab.

4. Open the scenario row you want to inspect.

5. For a failed scenario, choose Debug with AI. For a passed or skipped scenario, choose Open Playwright trace.

Either action opens the trace in the Playwright trace viewer. Debug with AI also docks an AI assistant beside the viewer that analyzes the trace and starts diagnosing the failure automatically. If a scenario has no trace, the Open Playwright trace action is not shown for that row.

What to inspect in a trace

Trace area	Use it for
Actions	See each Playwright click, fill, navigation, and assertion.
Snapshots	Inspect the page around each action.
Timeline	Find slow actions, timeouts, and late-loading resources.
Console	Match browser errors to a specific moment in the test.
Network	See requests and responses near the failing action.
Attachments	Review screenshots or other files tied to the run.

Download traces

When a run uploads trace files, you can download them from the Artifacts tab (or the per-scenario Artifacts list in the row details). Use this when a teammate needs the raw trace file or when you want to keep a copy outside TestVibe.

For the visible browser state around a failure, see View screenshots.