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

# Test

**Test** is where you find out whether the agent actually does what you intended — before it reaches real users.

Testing an agent is not like testing ordinary software. The same input can produce different output, so a single successful run proves very little. What you need is a scored dataset of representative cases, run repeatedly as you change instructions, skills, and behavior settings, so you can see whether a change improved the agent or merely moved the problem.

* [Evals](/agent-builder/test/evals.md) — Test the agent against scored datasets before release.

You can also exercise the agent interactively with **Try Agent** in the builder, and open the execution trace to see how it interpreted your instructions, which skills it called, and how long each step took. Use interactive testing to explore and evals to prove.

***

When the agent performs on your test cases, move on to [Deploy](/agent-builder/deploy.md). After release, [Monitor](/agent-builder/monitor.md) tells you how it behaves on traffic your test set never anticipated.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uptiq.ai/agent-builder/test.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.