> 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/inspect-failed-steps.md).

# 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 **Features** tab.
4. Find the failed scenario rows when the run has many.
5. Open the failed row to expand its details.

The details view can show the scenario location, the error, the final screenshot, the video, and a **Debug with AI** button that opens the Playwright trace with an AI assistant.

## Read the failure panel

Use the panel from top to bottom:

| Area             | What to look for                                                                                                                 |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Error            | The Playwright error text, assertion output, and the failure source.                                                             |
| Location         | The spec file and configuration that identify where the failure occurred.                                                        |
| Final screenshot | The browser state at the end of the failed scenario.                                                                             |
| Video            | The browser session leading up to the failure.                                                                                   |
| Debug with AI    | Opens the full action-by-action Playwright trace with an AI assistant docked beside it that diagnoses the failure automatically. |

## 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 session 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 console errors or network requests        | [Open traces](/results/open-traces.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
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/inspect-failed-steps.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.