the test suite and master test suite are now part of a more general
section about the test tree. The constraints on the tree are now
visible on the TOC.
To ease the creation of contexts, variadic let us declare several
values in one call (no extra brace) while ticky context let us
add new information while they arrive.
The example shows a random trial making a test fail. We force the failure
for the unit tests, which does not remove the documentation value of the
example.
- BOOST_TEST_GLOBAL_FIXTURE explained
- BOOST_TEST_GLOBAL_INITIALIZATION explained
- changed the examples, deprecating BOOST_GLOBAL_FIXTURE
- in the logger part, introduced the fact that BOOST_TEST_GLOBAL_INITIALIZATION should be used and no assertion is supported in this case
* topic/12540-printing-types-customisation-point:
Change log update
Documenting the customization point
Fixing the tests and checking everything works ok
Test for customization points
Customization points for printing user defined types through `boost_test_print_type`
- now experiencing the same behaviour as pre 1.62
- set_stream and set_threshold_level for the loggers are now mutating all loggers, not only the active ones
- renamed function
- when adding a custom logger, it is added to the set of loggers with CUSTOM
- updated the documentation
- major reorganization of the output section
- making more clear what a log and what a report is
- checkpoints doc update
- links to API, improved doxygen documentation and reference
- renamed files and sections
- JUNIT additional doc
- removed useless parts
