# 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, trace, or request evidence | 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.

## Download reports and artifacts

The run detail download menu appears when downloadable artifacts are available. Depending on what the run produced, options may include:

| Export                    | Use it for                                              |
| ------------------------- | ------------------------------------------------------- |
| Traces                    | Debugging a failed test in the Playwright trace viewer. |
| HTML Report               | Reviewing the Playwright report outside TestVibe.       |
| Blob Report               | Combining or processing Playwright report output.       |
| PDF, JSON, or XML reports | Sharing summaries or integrating with other tools.      |
| Report archives           | Keeping a bundle of available report files.             |

If an option is not shown, that artifact was not produced, is not available yet, or is no longer available.

## Share visual or request evidence

You can also share specific evidence:

| Evidence         | How to use it                                                           |
| ---------------- | ----------------------------------------------------------------------- |
| Screenshot       | Open the image preview and download it when available.                  |
| Video            | Open the Videos tab and use the matching video row.                     |
| Trace            | Use **Open Trace** or download trace artifacts from the run menu.       |
| Network response | Open the request details and download the response body when available. |
| Console errors   | Copy the relevant message and include the test row it came from.        |

## 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: 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:

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

The question should be specific, self-contained, and written in natural language.
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.