Some programs, including some test suites, produce no output in case of correct operation, and only produce output in the form of error messages if something has gone wrong.

This makes for nice, non-verbose, tools.

Unfortunately, bugs can also reduce (result?) in code being skipped and no output produced. Therefore, for test suites, it is a good idea to provide TestPositiveConfirmation, i.e. to indicate
	* when a test starts running,
	* when a test has failed,
	* when a test has passed,
	* when it stops running.

Summarizing these positive confirmations can be done via counts.

----

I have occasionally used multilayer or folded output formats, to hide details but still make them available.

E.g.
	* All tests passed
		* 2 test suites passed
			* Test Suite 1 passed
				* 4 test cases
					* test case 1 ...
			*  Test Suite 2 passed
				* ...

----
CategoryTesting