> 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/agentic-testing.md).

# Agentic testing

AI agents working with your CI test runs in Currents: fix failing tests, prove a change with the tests that cover it, and share a run

Use these pages when a CI test covers the change. If no test covers it, see [Agent evidence](/ai/agent-evidence.md).

Your CI already reports each test run to Currents, with its errors, steps, screenshots, videos and traces. Connect an agent to the [Currents MCP server](/ai/connect.md), and it works from that recorded data instead of the CI log. The agent does not have to run the tests again to see what happened, and it gives you links to the files it used.

| You want to                                                       | Read                                                                  |
| ----------------------------------------------------------------- | --------------------------------------------------------------------- |
| Hand a failing CI test to an agent, with the full failure context | [Fix failing CI tests](/ai/agentic-testing/fix-failing-tests.md)      |
| Prove a change works with the CI tests that cover it              | [Prove a change with CI tests](/ai/agentic-testing/prove-a-change.md) |
| Share the recording of a CI run with a colleague or an agent      | [Share a CI run](/ai/agentic-testing/share-a-run.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/agentic-testing.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.