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
Raw : Returns the raw structure representation of the testing results
Simple : A basic HTML reporter
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 minimalistic view of your test reports
To use a specific reporter append the reporter
variable to the url string. ex &reporter=Text
However, you can also build custom reporters very easily.
You can also build your own reporters by implementing our core class: testbox.system.reporters.IReport
Once you implement your own report you just need to pass the class path or the instance of your reporter to the TestBox runner methods using the reporter
argument. The reporter
argument can be the following values:
string
- The class path of your reporter
instance
- The instance of your reporter CFC
struct
- A structure representing your reporter with the following keys: { type="class_path", options={}
. This is mostly used if you want to instantiate and use your reporter with a structure of options.
Now you can init TestBox with your reporter:
Here is a sample reporter for you that generates JSON for the output.