> For the complete documentation index, see [llms.txt](https://testbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://testbox.ortusbooks.com/getting-started/testbox-bdd-primer/reporters.md).

# Reporters

TestBox comes also with a nice plethora of reporters:

* **ANTJunit** : A specific variant of JUnit XML that works with the ANT junitreport task
* **Codexwiki** : Produces MediaWiki syntax for usage in Codex Wiki
* **Console** : Sends report to console
* **Doc** : Documentation-style HTML with a bundle navigation, in light and dark
* **Dot** : One dot per spec, click a dot for its details and Ask AI
* **JSON** : Builds a report into JSON
* **JUnit** : Builds a JUnit compliant report
* **Raw** : Returns the raw structure representation of the testing results
* **Simple** : The complete HTML report, failures first, with Ask AI and editor links
* **Text** : Back to the 80's with an awesome text report
* **XML** : Builds yet another XML testing report
* **Tap** : A test anything protocol reporter
* **Min** : A compact HTML view that lists only what needs attention
* **MinText** : A minimalistic view of your test reports in consoles
* **Agent** : Compact, token-efficient JSON for AI agents and automation
* **NodeJS** : User-contributed: <https://www.npmjs.com/package/testbox-runner>

The HTML reporters (Simple, Min, Dot and Doc) were rebuilt in TestBox 7.2 with light and dark themes, keyboard navigation and **Ask AI** on every failure.

<figure><img src="https://2482745662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5kuiG5ZXNT2hNA83299A%2Fuploads%2Fgit-blob-818603d285b2c6afb9b098d51cabcb9c81d66060%2Freporters-simple-failures-light.png?alt=media" alt="The Simple reporter"><figcaption><p>The Simple reporter</p></figcaption></figure>

{% content-ref url="/pages/zqxNSVtrAu3AReVnO0ZN" %}
[HTML Reporters](/digging-deeper/reporters/html-reporters.md)
{% endcontent-ref %}


---

# 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://testbox.ortusbooks.com/getting-started/testbox-bdd-primer/reporters.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.