Override to run code before tests start running.
Override to run code before tests start running. Useful for setting up global databases, initializing caches, etc.
How many tests need to run before uTest starts printing out the test results summary and test failure summary at the end of a test run.
How many tests need to run before uTest starts printing out the test results summary and test failure summary at the end of a test run. For small sets of tests, these aren't necessary since all the output fits nicely on one screen; only when the number of tests gets large and their output gets noisy does it become valuable to show the clean summaries at the end of the test run.
Override to run code after tests finish running.
Override to run code after tests finish running. Useful for shutting down daemon processes, closing network connections, etc.
Whether to use SBT's test-logging infrastructure, or just println.
Whether to use SBT's test-logging infrastructure, or just println.
Defaults to println because SBT's test logging doesn't seem to give us anything that we want, and does annoying things like making a left-hand gutter and buffering input by default
(Since version ) see corresponding Javadoc for more information.