# 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. |
| Tests tab                | Individual test rows and failed scenarios.                          |
| Images and Videos tabs   | Browser evidence captured during the run.                           |
| Network and Console tabs | Technical evidence from the browser session.                        |
| Download menu            | Reports and artifact bundles when the run produced them.            |

## 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>Use console logs, network requests, and traces when the cause is not visible.</td><td><a href="/pages/xIcdsE0KMMQ7bdQJyP3o">/pages/xIcdsE0KMMQ7bdQJyP3o</a></td></tr></tbody></table>

## A Good Review Flow

1. Confirm the overall run status.
2. Filter to failed rows in the Tests tab.
3. Open the failed row details.
4. Check the screenshot or video for visible UI state.
5. Open the trace, console, or network evidence when the screenshot is not enough.
6. Decide whether the issue is the app, the test, the environment, or the runner.
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: 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.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.