> 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/platform/testing.md).
# Testing
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](/agents/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 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.spara.com/platform/testing.md?ask=&goal=
```
`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.