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

# Test Run Report

For each test run, you can download a shareable PDF report. This report provides details about your test target, along with an overview and summary of the test run. It includes general information such as the start time, execution time, total number of test cases, and more. Additionally, it features the combined results and a chart of all probe runs, offering a clear, one-stop insight into the target’s vulnerabilities.

The report also provides specific results for each probe run and their suggested mitigation strategies, helping you understand vulnerabilities and how to fix them.

The Test Run Report can be automatically emailed upon completion of the test run, provided that [**Test Run Notification**](/ai-red-teaming/probe/test-run.md#test-run-notifications) is enabled.

{% hint style="info" %}
Generating the report may take up to 2 minutes, depending on the amount of data.
{% endhint %}

To download the report, click the **Generate Report** button on the [**Test Run View**](/ai-red-teaming/probe/test-run/test-run-view.md) page.


---

# 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.probe.splx.ai/ai-red-teaming/probe/test-run/test-run-report.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.