# 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` : Builds semantic HTML to produce nice documentation
* `Dot` : Builds an awesome dot report
* `JSON` : Builds a report into JSON
* `JUnit` : Builds a JUnit compliant report
* `Min` : A minimalistic view of your test reports
* `MinText` : A minimalistic text report
* `Raw` : Returns the raw structure representation of the testing results
* `Simple` : A basic HTML reporter
* `Tap` : A test anything protocol reporter
* `Text` : Back to the 80's with an awesome text report
* `XML` : Builds yet another XML testing report

To use a specific reporter append the `reporter` variable to the `url` string. ex `&reporter=Text` or set it in your `runner.cfm`

## Open In Editor (Simple)

The `simple` reporter allows you to set a code editor of choice so it can create links for stack traces and tag contexts. It will then open your exceptions and traces in the right editor at the right line number.

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

To change the editor of choice use the `url.editor` parameter which you can send in via 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/-MaVmVbIdGJPPFmoQL3r)

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

### Available Editors

The available editors are:

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

## `Images`

![](/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/v6.x/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.