The output produced by a test module is one of the major assets the Unit
Test Framework brings to users. In comparison with any kind of manual/assert
based solution the Unit Test Framework provide following
services:
-
All test errors are reported uniformly
The test execution monitor
along with standardized output from all included testing
tools provides uniform reporting for all errors including fatal
errors, like memory assess violation and uncaught exceptions.
-
Detailed information on the source of an error
The Unit
Test Framework test tool's based assertion provides as much
information as possible about cause of error, usually allowing you to deduce
what is wrong without entering the debugger or core analysis.
-
Separation of the test errors description (test log) from the results report
summary (test results report) The information produced during test execution,
including all error, warning and info messages from the test tools, executed
test units notification constitute the test log. By default all entries
in the test log are directed to the standard output. Once testing is completed
the Unit Test Framework may produce a summary test
report with different levels of detail. The test report is by default directed
to the standard error output.
-
Flexibility in what is shown in the output
The Unit Test
Framework provides the ability to configure what is shown in
both the test log and the test report. The configuration is supported both
at runtime, during test module invocation and at compile time from within
a test module.
-
Flexibility in how output is formatted
The Unit Test Framework
provides the ability to configure the format of the test module output.
At the moment only 2 formats are supported by the Unit Test Framework
itself, the well defined public interface allows you to customize an output
for your purposes almost any way you want.
|
Tip |
More details about the class implementing the formatting of the logs can
be found in the following reference sections.
|