# View screenshots

Screenshots show what the browser looked like during the run. They are especially helpful when a test fails because they show whether the app was on the expected page, whether an element was visible, and what message or state the user would have seen.

## Where screenshots appear

You may see screenshots in two places:

| Place              | Use it for                                               |
| ------------------ | -------------------------------------------------------- |
| Failed row details | Review the screenshot matched to a specific failed test. |
| Images tab         | Browse image artifacts captured for the whole run.       |

Open **Runs**, select a run, then open the failed row details or the **Images** tab.

## How to review a screenshot

Look for the visible state that explains the result:

| What to check                | Why it matters                                             |
| ---------------------------- | ---------------------------------------------------------- |
| Current page                 | Confirms whether the test reached the expected screen.     |
| Error messages               | Shows validation errors, server errors, or login failures. |
| Missing elements             | Explains selector and visibility failures.                 |
| Unexpected modals or banners | Can block clicks and assertions.                           |
| Responsive layout            | Helps identify viewport-specific behavior.                 |

Click an image to open a larger preview. From the image viewer, use download when you need to attach the screenshot to a bug report or discussion.

## Compare with the failed step

A useful screenshot review connects the image to the test step:

1. Read the failed row or error message.
2. Open the screenshot.
3. Identify what the test expected to see or do.
4. Compare that expectation with the actual page state.
5. Decide whether the app, test, data, or environment needs the change.

## If screenshots are missing

Screenshots may be unavailable when:

| Reason                                          | What to check                                  |
| ----------------------------------------------- | ---------------------------------------------- |
| The run is still finalizing                     | Wait for artifact processing to finish.        |
| The run configuration does not save screenshots | Review the selected run configuration.         |
| Screenshots are saved only on failure           | Passed tests may not produce screenshots.      |
| The workflow failed before Playwright ran       | Check runner setup, dependencies, and secrets. |
| Artifacts expired or were deleted               | Use a newer run or re-run the test.            |

For video evidence, see [Watch videos](/results/watch-videos.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/view-screenshots.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.