Runs the test.
Runs the test. The TAP stream will be written to Console.out and Console.err, so you can swap these out as required in order to parse it.
The exit code that the test produced. Success is indicated by 0,
failure to run the correct number of tests by 255, and any other
failure by the number of tests that failed. This should be used
by reporters which run a single test, which can call
sys.exit(exitCode)
Runs the test just like run, but in a way that makes sense when test results are being summarized rather than directly displayed.
Runs the test just like run, but in a way that makes sense when test results are being summarized rather than directly displayed.
Summarizing test reporters tend to repeatedly update the same line on the terminal, so this method makes calls to diag (which sends messages to stderr, where they are typically displayed as-is) prefix the message with a newline, to ensure that the output starts on its own line.
Runs an external process which emits TAP, and parses it as a test.
This test class can be used if you have existing tests that you would like to be able to include in a test suite using this framework. You just need to write a test class for each external test that looks like this:
This will run your external process, and use its TAP stream as its output. This will allow it to, for instance, be a part of the test suite that runs via
sbt test. As with any other test class, its stdout and stderr will be sent toConsole.outandConsole.err, where they can be overridden as needed.