# Inspect failed steps

Failed rows are the starting point for triage. A failure may mean the application has a bug, the test needs an update, the target environment is not ready, or a shared dependency such as login or test data failed.

## Open failure details

1. Open **Runs**.
2. Select the failed run.
3. Open the **Tests** tab.
4. Filter to **Failed** when the run has many rows.
5. Open the failed row details.

The details view can show the test location, failure reason, screenshot, error text, and an AI summary when one is available.

## Read the failure panel

Use the panel from top to bottom:

| Area           | What to look for                                                                           |
| -------------- | ------------------------------------------------------------------------------------------ |
| Location       | File, line, project, or configuration metadata that identifies where the failure occurred. |
| Failure reason | The shortest explanation TestVibe has for the failed row.                                  |
| Screenshot tab | The browser state near the failure.                                                        |
| Error tab      | Playwright error text, assertion output, or stack information.                             |
| Edit Test      | Opens the test when the failure indicates the test itself needs an update.                 |

## Decide what kind of failure it is

| Signal                                                      | Likely cause                                                       |
| ----------------------------------------------------------- | ------------------------------------------------------------------ |
| Screenshot shows the wrong page                             | Navigation, login, or environment setup may be wrong.              |
| Screenshot shows the expected page but the assertion failed | The test expectation may be too strict or out of date.             |
| Error mentions missing selector or timeout                  | The UI changed, the app was slow, or the selector needs an update. |
| Error appears before the test reaches the app               | Check runner setup, dependencies, and secrets.                     |
| Many rows fail at the same prerequisite                     | Fix the prerequisite before editing individual tests.              |

## Use the next evidence layer

If the failure panel does not explain the problem:

| Need                                                    | Open                                                                         |
| ------------------------------------------------------- | ---------------------------------------------------------------------------- |
| See the exact browser sequence                          | [Watch videos](/results/watch-videos.md)                                     |
| Inspect page actions, DOM snapshots, and request timing | [Open traces](/results/open-traces.md)                                       |
| Check browser JavaScript errors                         | [Review console and network details](/results/review-console-and-network.md) |
| Check API failures or missing assets                    | [Review console and network details](/results/review-console-and-network.md) |

After you make a change, re-run the smallest useful scope first. For re-runs, see [Cancel or re-run tests](/run-tests/cancel-or-rerun-tests.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/inspect-failed-steps.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.