# Review your first result

After the run finishes, open the result details. This is where TestVibe helps you understand what happened.

The goal is not only to see pass or fail. The goal is to know what to do next.

## Start With The Summary

Look for:

* overall status
* number of tests or scenarios that passed or failed
* run duration
* selected browser and viewport
* site URL
* any visible error or failure message

If the run passed, you can keep building coverage. If it failed, inspect the evidence before editing the test.

## Review Evidence

Depending on the run and configuration, TestVibe may show:

| Evidence        | How it helps                                         |
| --------------- | ---------------------------------------------------- |
| Screenshots     | Show what the page looked like at important moments. |
| Videos          | Replay the browser session.                          |
| Trace           | Inspect Playwright actions, snapshots, and timing.   |
| Console output  | Find browser errors or warnings.                     |
| Network details | Check failed requests or unexpected responses.       |
| Failure details | See which step or expectation did not pass.          |

For deeper review guidance, see [Review Results](/results.md).

## Decide What To Do Next

Use the result to choose the next action:

| If you see...                                   | Consider...                                                      |
| ----------------------------------------------- | ---------------------------------------------------------------- |
| The test passed                                 | Add another test or run a group.                                 |
| The expected UI did not appear                  | Check whether the application has a real issue.                  |
| The test clicked or checked the wrong thing     | Improve the Gherkin instructions and regenerate.                 |
| Test data was missing                           | Update setup, prerequisites, or the target environment.          |
| The site URL was wrong                          | Update the run or repository settings and run again.             |
| The generated code is close but not quite right | Edit the instructions, regenerate, or review the generated code. |

## Build From Your First Run

Once one test works, the next step is to expand carefully:

1. Add another scenario in the same feature.
2. Generate and run it.
3. Add a related group or feature.
4. Run a small group.
5. Move toward scheduled or full-suite runs when the basics are stable.

## Next

You have completed the quickstart. Good next pages are:

* [Create groups and tests](/create-tests/create-groups-and-tests.md)
* [Generate Playwright code](/ai-generation/generate-playwright-code.md)
* [Run a group](/run-tests/run-group.md)
* [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/quickstart/review-first-result.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.