> For the complete documentation index, see [llms.txt](https://docs.getantidote.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getantidote.com/welcome-to-antidote/getting-started/review-results.md).

# Review Results

Review the state graph, errors, and screenshots from an exploration.

Once an exploration completes, open the product's **Runs** tab and pick it from the runs table, or open it from **Recent runs** on the Overview. When [Releases](/welcome-to-antidote/viewport-dashboard/releases.md) are enabled, open the release from [Releases](/welcome-to-antidote/viewport-dashboard/releases.md) and choose the run under **Exploration runs**.

Open a run there to inspect what Antidote found.

### What to review

#### State graph

The graph shows every discovered page and how states connect. Nodes are states. Edges are actions like clicks, form submissions, and navigations.

#### Run replay

Each run includes a live recording of the full browser session.

Use it to watch every step Antidote took, see where a flow changed, and confirm what happened before an error appeared.

#### Errors

Review:

* Runtime errors
* Network request failures
* Broken interactive elements
* Console errors and warnings
* Visual issues - bugs visible on the screen

Each error includes the page where it occurred and a screenshot from that state.

#### Screenshots

Every state transition includes a full-page screenshot. Use them to verify what Antidote actually saw.

{% hint style="info" %}
One exploration gives you a useful snapshot. Multiple explorations improve graph coverage over time.
{% endhint %}

### Continue with

* [Goals & Intent Tests](/welcome-to-antidote/core-concepts/goals-and-intent-tests.md)
* [GitHub Action](/welcome-to-antidote/integrations/github-actions/ci-integration-with-github-actions.md)
* [API Keys](/welcome-to-antidote/integrations/api-keys.md)