> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/build/testing.md).
# Testing
How to test Spara AI.
The [Testing](https://app.spara.co/tests) page lets you try out any agent (before or after it goes live) and review past test sessions in one place.
Click **Test** to start a session. Choose the **Agent Type** (such as Chat or Phone), the specific **Agent** to test (including unpublished **drafts**), and the **Interface** to run it in. Spara loads a test conversation where you can interact exactly as a lead would.
Give feedback on any Spara-generated response by clicking the thumbs up or thumbs down button on a message. A modal appears with fields to enter your feedback, which is used to improve Spara AI's performance.
Past test sessions are listed below the controls (the agent tested, its published/draft status, who ran the test, and when), so your team can revisit earlier runs.
The Testing page: start a test for any agent and interface, and review past sessions.
To test a single capability from inside its editor and run automated Simulations, see [Testing](/build/channels/configuring/testing.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.spara.com/build/testing.md?ask=&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.
