# Reporters

TestBox ships with a rich set of reporters for every use case:

| Reporter    | Description                                                  |
| ----------- | ------------------------------------------------------------ |
| `ANTJunit`  | JUnit XML variant compatible with the ANT `junitreport` task |
| `Codexwiki` | MediaWiki syntax for use in Codex Wiki (DEPRECATED)          |
| `Console`   | Sends the report to the console                              |
| `Doc`       | Semantic HTML for documentation-style output                 |
| `Dot`       | Compact dot-matrix report (DEPRECATED)                       |
| `JSON`      | Full JSON report of all results                              |
| `JUnit`     | Standard JUnit-compliant XML report                          |
| `Min`       | Minimalistic HTML view                                       |
| `MinText`   | Minimalistic plain-text report                               |
| `Raw`       | Raw BoxLang/CFML struct representation of results            |
| `Simple`    | Basic HTML reporter with editor link support                 |
| `Tap`       | Test Anything Protocol (TAP) output (DEPRECATED)             |
| `Text`      | Full plain-text report                                       |
| `XML`       | XML-based testing report                                     |

To use a specific reporter, append `reporter` to your runner URL, e.g. `&reporter=Text`, or set it in your `runner.bxm` / `runner.cfm`.

## `ConsoleReporter` — Hiding Skipped Tests

The `ConsoleReporter` now accepts a `hideSkipped` option (default `false`) that suppresses skipped spec output — useful when you have many pending specs and want cleaner terminal output.

```javascript
var testbox = new testbox.system.TestBox(
    bundles  = "tests.specs",
    reporter = {
        type    : "testbox.system.reports.ConsoleReporter",
        options : { hideSkipped : true }
    }
);
```

When using the BoxLang CLI runner, pass `--show-skipped=false` instead:

```bash
./testbox/run --show-skipped=false
```

## `StreamingReporter` — Real-Time SSE Output 🆕

The new `StreamingReporter` (backed by `StreamingRunner`) pushes each spec result to the client in real time via Server-Sent Events. It powers both the [TestBox RUN IDE](/getting-started/running-tests/testbox-run-ide.md) and the `testbox run --streaming` command.

{% content-ref url="/pages/2RZVKzZXXh182rLMwI02" %}
[Streaming Runner](/getting-started/running-tests/streaming-runner.md)
{% endcontent-ref %}

## Open In Editor (Simple Reporter)

The `simple` reporter allows you to set a code editor of choice so it creates clickable links for stack traces and tag contexts — opening exceptions in your editor at the exact line.

{% hint style="info" %}
The default editor is `vscode`.
{% endhint %}

Use the `url.editor` parameter in the URL or set it in your `runner.cfm`:

```markup
<cfsetting showDebugOutput="false">
<!--- Executes all tests in the 'specs' folder with simple reporter by default --->
<cfparam name="url.reporter" 			default="simple">
<cfparam name="url.directory" 			default="tests.specs">
<cfparam name="url.recurse" 			default="true" type="boolean">
<cfparam name="url.bundles" 			default="">
<cfparam name="url.labels" 				default="">
<cfparam name="url.excludes" 			default="">
<cfparam name="url.reportpath" 			default="#expandPath( "/tests/results" )#">
<cfparam name="url.propertiesFilename" 	default="TEST.properties">
<cfparam name="url.propertiesSummary" 	default="false" type="boolean">
<cfparam name="url.editor" 				default="vscode">

<!--- Include the TestBox HTML Runner --->
<cfinclude template="/testbox/system/runners/HTMLRunner.cfm" >
```

![](/files/-MaVlM2aFLh6382FRCxN)

![](/files/-MaVmXxiKn-8rFkgBNtd)

### Available Editors

* atom
* emacs
* espresso
* idea
* macvim
* sublime
* textmate
* vscode
* vscode-insiders

## Reporter Screenshots

![](/files/-LA-UpNU9hgC1w_ftvqF)

![](/files/-LA-UpNV2-KMZgOgesmK)

![](/files/-LA-UpNWI_EmyabCvTrM)

![](/files/-LA-UpNX2Eoawn-e3TRR)

![](/files/-LA-UpNYSlB_A-Ka-2mR)

![](/files/-LA-UpNZqtTcg5TAVVEM)


---

# Agent Instructions: 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:

```
GET https://testbox.ortusbooks.com/digging-deeper/reporters.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.