> 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.md).

# Review Results

Use this section after a run starts or finishes. TestVibe brings the run status, test rows, charts, and evidence into one run detail view so you can decide what passed, what failed, and what to do next.

## Start With the Run Detail

Open **Runs**, then select a run from the list. The run detail view shows:

| Area                   | What it tells you                                                                                                                                                          |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Summary tiles          | Overall status, duration, selected files, and pass/fail counts.                                                                                                            |
| Charts                 | Patterns across status, groups, projects, duration, and slow tests.                                                                                                        |
| Features tab           | Individual scenario rows and failed scenarios.                                                                                                                             |
| Images and Videos tabs | Browser evidence captured during the run.                                                                                                                                  |
| Artifacts tab          | Every file the run uploaded (screenshots, video, traces, logs), each downloadable — grouped by the scenario that produced it so you don't have to match filenames by hand. |
| Download menu          | Export the run as JSON, CSV, Excel, PDF, or PNG.                                                                                                                           |
| Ask AI                 | Seeds the Assistant with a data-rich summary of the run — a quick way to get a plain-English verdict or share one with a teammate.                                         |

## Common Review Tasks

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Read status</strong></td><td>Understand passed, failed, cancelled, skipped, and mixed run outcomes.</td><td><a href="/pages/V2aqM0r3jCbp5jCjqhg0">/pages/V2aqM0r3jCbp5jCjqhg0</a></td></tr><tr><td><strong>Inspect a failure</strong></td><td>Open a failed row and review the error, location, screenshot, and next action.</td><td><a href="/pages/XXC6Gb4aKVlwEOVrMnLK">/pages/XXC6Gb4aKVlwEOVrMnLK</a></td></tr><tr><td><strong>Use visual evidence</strong></td><td>Compare screenshots and videos against the step that failed.</td><td><a href="/pages/YJIWDkFoxfPVhDCyu0SD">/pages/YJIWDkFoxfPVhDCyu0SD</a></td></tr><tr><td><strong>Debug deeper</strong></td><td>Open the Playwright trace to inspect actions, snapshots, console, and network around a failure.</td><td><a href="/pages/y4JFvPXNCw5WGEFAaoEC">/pages/y4JFvPXNCw5WGEFAaoEC</a></td></tr></tbody></table>

## A Good Review Flow

1. Confirm the overall run status.
2. Find the failed rows in the Features tab.
3. Open the failed row details.
4. Check the screenshot or video for visible UI state.
5. Open the Playwright trace when the screenshot is not enough.
6. Decide whether the issue is the app, the test, the environment, or the cloud test session.
7. Re-run only after you know what changed.

For active runs, see [Understand live run status](/run-tests/understand-live-run-status.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.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.