Tests can be reported in a variety of different ways.
When you run a test script directly, it’ll always output TAP. The tap runner will interpret this output, and can format it in a variety of different ways.
These are done programmatically using the tap-mocha-reporter module, which ports many of the report styles built into mocha.
You can specify a reporter using the
The following options are available:
The default when stdout is a terminal. Show a summary of each test file being run, along with reporting each failure and pending test.
Just the raw TAP. Default when stdout is not a terminal.
Output heirarchical HTML.
Output a dot for each pass and failure.
Mostly for debugging tap-mocha-reporter, dumping out the TAP output and the way that its being interpreted.
Output results in one big JSON object.
Output results as a stream of
A unicode airplane that lands on your terminal.
List out each test as it’s run.
Heirarchical markdown output with a table of contents.
Just the post-test summary of failures and test count.
A magical cat who is also a toaster pastry.
A progress bar.
Output absolutely nothing
Output based on rspec, with heirarchical indentation and unicode red and green checks and X’s.
XML output popular in .NET land.