Share or Export Results
Share a run by link or email summary, export it as JSON, CSV, an Excel workbook, a PDF report or a PNG snapshot, and open the Artifacts tab for the raw screenshots, video and trace.
Good failure reports include the smallest set of details that lets someone else understand and reproduce the issue.
What to include
When sharing a result, include:
| Detail | Why it helps |
|---|---|
| Run status | Shows whether the run passed, failed, cancelled, or is still active. |
| Site URL | Identifies the environment that was tested. |
| Test or group name | Narrows the scope to the affected scenario. |
| Run configuration | Explains browser, viewport, and evidence settings. |
| Failure reason | Gives the shortest available explanation. |
| Screenshot, video, or trace | Lets the teammate see the failure without re-running first. |
Share a run
- Open Runs.
- Select the run you want to discuss.
- Copy the useful run details from the summary and failed row.
- Attach or link the relevant evidence.
If your team uses GitHub issues, Jira, Slack, Teams, or another workspace tool, paste the run context there with the failed test name and evidence.
Export the run
The run detail Download menu exports the run so you can share it outside TestVibe:
| Export | Use it for |
|---|---|
| Results (JSON) | A machine-readable copy of the run, scenarios, and artifact links. |
| Scenarios (CSV) | A spreadsheet of each scenario's status, duration, and error. |
| Excel workbook | A summary plus scenario and artifact sheets in one file. |
| PDF report | A shareable snapshot of the run detail view. |
| PNG snapshot | An image of the run detail view for chats or tickets. |
To download the run's raw files — screenshots, video, traces, and logs — open the Artifacts tab, where each file is individually downloadable. Traces also open directly in the Playwright trace viewer.
Share visual evidence
You can also share specific evidence:
| Evidence | How to use it |
|---|---|
| Screenshot | Open the image preview and download it from the Images tab or the row details. |
| Video | Open the Videos tab and use the matching video row. |
| Trace | Use Debug with AI (failed scenarios) or Open Playwright trace (passed scenarios) to open the trace viewer, or download the trace file from the Artifacts tab. |
Keep the report focused
A clear report usually answers:
- What was tested?
- What failed?
- What did the browser show?
- Which evidence proves it?
- What changed before the failure, if known?
For interpreting failures before sharing, see Inspect failed steps.