# TestFailureDetails

**Help URL:** `/forms/test-failure-details`

## Purpose

Inspect a failed test with the most relevant evidence gathered from the run.

## Common Tasks

* Read the failure message.
* Identify the failed step or assertion.
* Open screenshot, video, trace, console, or network evidence when available.
* Decide whether to fix the app, edit the test, regenerate, or re-run.

## Key UI Elements

* Failure summary: The short explanation of what failed.
* Error details: The Playwright or workflow message.
* Evidence links: Open artifacts such as screenshots, videos, traces, console, and network details.
* Close: Returns to the run result.

## Notes

* Start with the screenshot or video for visible UI failures.
* Use traces, console, and network details when the visible state does not explain the failure.
* See [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/reference/forms/test-failure-details.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.