The Unit Test Framework supports several log formats:
human readable format
an machine interpretable log format
a standardized log format understandable by automated tools such as Continuous
The following functionalities are supported by the logging framework:
each logger manages its own log level. The rationale is that some log
format are meant for automated processing, and by design need to carry
all the information that will later be digested by a visualization tool.
several log format may be active at the same time. The rationale is that
the user might want to see a non-exhaustive log in his terminal using
a human friendly format, while having a detailed full log in a file with
a format dedicated to automated processing.
each logger indicates its default output stream.
some logger may prefer to output to one of the standard stream while
other may prefer output to a file.
The logger indicates the default output stream in case the default should
By default the active log level threshold is set to "non
fatal error messages" and the test log output is generated in
The active log level threshold and the output format can be configured at
runtime during a test module invocation and at compile time from within a
test module using the test
log public interfaces.