![]() |
Home | Libraries | People | FAQ | More |
Parameter log_level allows to set the Unit Test Framework log level. Log level defines the verbosity of the testing log produced by a testing module. The verbosity ranges from a complete log, when all assertions (both successful and failing) are reported and all notifications about test units start and finish are included, to an empty log, when nothing is reported to a testing log stream.
Log level is set to one of the predefined levels which are organized hierarchically, where each level includes all the messages on that level as well as all the messages from levels below. Levels are identified by string names, which are listed next.
Following is the list of enumeration log_level names ordered from higher to lower level. Thus each level includes messages on that level as well as all the messages on levels defined below.
Value |
Included messages |
---|---|
all (default for JUNIT) |
All log messages including the passed assertions notification |
success |
The same as all |
test_suite |
Test units start/finish notifications |
message |
User generated messages (using |
warning |
Messages describing failed assertion on |
error (default for HRF and XML) |
Messages describing failed assertion on |
cpp_exception |
Messages reporting uncaught C++ exception |
system_error |
Messages reporting system originated non-fatal errors. For example, timeout or floating point exception. |
fatal_error |
Messages reporting user or system originated fatal errors. For
example, memory access violation. Also all the messages describing
failed assertion on |
nothing |
No messages are reported. |
![]() |
Caution |
---|---|
the JUNIT log format does not accept the log level to change: anything
specified by |
--log_level=<level>
-l
<level>
BOOST_TEST_LOG_LEVEL