> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/auditors/managing-internal-audits-apps/managing-testing.md).

# Managing Testing

Define how requirements are evaluated and what evidence supports the results.

Use the **Testing Management** category to manage tests and their associated evidence. 

* **Tests** define how requirements are evaluated.
* **Evidence** defines the data or documentation collected during testing.

{% hint style="warning" %}
For a requirement to be included in testing, it must be linked to a test with associated evidence.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Test Evidence Management</strong></td><td>Create and manage evidence used to support audit testing.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FiNfFoKTRdSmcgl6kW3hk%2FIMS-V16-NAV-Library-Icons-164.png?alt=media&amp;token=cbd2bbef-368e-40d9-bd6f-acc567cb8296">IMS-V16-NAV-Library-Icons-164.png</a></td><td><a href="/interfacing-help-files/auditors/managing-internal-audits-apps/managing-testing/test-evidence-management.md">Test Evidence Management</a></td></tr><tr><td><strong>Create Test</strong></td><td>Create tests and link them to requirements and evidence.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FKmYpdVy8yOpVrIEQPlf0%2FCR-V16-Icons.png?alt=media&amp;token=ef97809d-5108-4c23-94cf-c0f1390e1908">App-V16-Icons.png</a></td><td><a href="/interfacing-help-files/auditors/managing-internal-audits-apps/managing-testing/create-test.md">Create Test</a></td></tr><tr><td><strong>All Tests</strong></td><td>Browse, filter, and manage all existing tests.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FfXk8vAHQXOIp5dHj6Hb6%2FIMS-V16-NAV-Library-Icons-163.png?alt=media&amp;token=2908c445-4f74-406b-9f50-f9ca85f4ecbf">IMS-V16-NAV-Library-Icons-163.png</a></td><td><a href="/interfacing-help-files/auditors/managing-internal-audits-apps/managing-testing/all-tests.md">All Tests</a></td></tr></tbody></table>


---

# 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://interfacing.gitbook.io/interfacing-help-files/auditors/managing-internal-audits-apps/managing-testing.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.