> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/results/share-or-export-results.md).

# Share or Export Results

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

1. Open **Runs**.
2. Select the run you want to discuss.
3. Copy the useful run details from the summary and failed row.
4. 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:

1. What was tested?
2. What failed?
3. What did the browser show?
4. Which evidence proves it?
5. What changed before the failure, if known?

For interpreting failures before sharing, see [Inspect failed steps](/results/inspect-failed-steps.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/results/share-or-export-results.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.