...one of the most highly
regarded and expertly designed C++ library projects in the
world.
— Herb Sutter and Andrei
Alexandrescu, C++
Coding Standards
The human readable log format is designed to closely match an errors description produced by the Microsoft family of C++ compilers. This format allows jumping to the error location, if test module output is redirected into IDE output window. The rest of the log messages are designed to produce the most human friendly description of the events occurring in test module. This is a default format generated by test modules.
Here the list of events along with corresponding message and the condition that has to be satisfied for it to appear in the output.
Event |
Condition |
Output |
---|---|---|
On testing start |
threshold != log_nothing |
|
On testing start |
threshold != log_nothing, show_build_info is set |
Platform: $BOOST_PLATFORM Compiler: $BOOST_COMPILER STL : $BOOST_STDLIB Boost : $BOOST_VERSION |
On abnormal testing termination |
threshold <= log_messages |
|
On test unit start |
threshold <= log_test_units |
|
On test unit end |
threshold <= log_test_units; testing time is reported only if elapsed time is more than 1 us. |
|
On skipped test unit |
threshold <= log_test_units |
|
On uncaught C++ exception |
threshold <= log_cpp_exception_errors. Checkpoint message is reported only if provided |
|
On resumable system error |
threshold <= log_system_errors. Checkpoint message is reported only if provided |
|
On fatal system error |
threshold <= log_fatal_errors. Checkpoint message is reported only if provided |
|
On passed test assertion |
threshold <= log_successful_tests |
|
On failed WARNING level test assertion |
threshold <= log_warnings |
|
On failed CHECK level test assertion |
threshold <= log_all_errors |
|
On failed REQUIRE level test assertion |
threshold <= log_fatal_errors |
|
On test log message |
threshold <= log_messages |
|
Advanced testing tools may produce more complicated error messages.