> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/ai/ai-in-the-dashboard/explain-this-test.md).

# Explain this test

Explain this test describes in plain words what a test does and what it checks, in the Currents dashboard

Explain this test describes in plain words what a test does and what it checks. An AI model writes it from what Currents recorded for the test: its title, spec file, steps and assertions. It does not read your repository. It helps when you review a failure in a test you did not write, or when the test name does not say enough.

Explain this test works on any test, passed or failed. It needs the **AI assistance** setting that also turns on [AI Failure Analysis](https://docs.currents.dev/ai/ai-in-the-dashboard/ai-failure-analysis.md#turn-on-ai-failure-analysis).

## Explain a test

1. Open a run and select any test.
2. In **Insights**, expand **Explain this test**.

The card shows a short summary of what the test verifies, what the test does step by step, and the checks it makes. When they are evident, it also lists the setup the test depends on and caveats such as retries.

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2Fgit-blob-a5132e0e5018ba3b64ba09bb0167f6666a781954%2Fai-explain-this-test.png?alt=media" alt="The Insights section of a test with Explain this test expanded: a one-line summary of what the test verifies, then What it does as numbered steps and What it checks as a list" width="720"><figcaption></figcaption></figure>

Currents keeps the result, so the next person who opens the same test sees it without a new request. Copy it to paste into a pull request, an issue or an agent prompt.

To find out why a failed test failed, use [AI Failure Analysis](https://docs.currents.dev/ai/ai-in-the-dashboard/ai-failure-analysis.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/ai/ai-in-the-dashboard/explain-this-test.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
