A few tests designed to deliberately fail appeal to UB (undefined
behavior), but as the MSVC optimizer improves we will take advantage of
that to remove UB statements. In order for deliberate failures to occur,
the tests must have the optimizer turned off.
- 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/doc-list-labels-content-update:
fix
cleanup
Doc: list_content/list_label enhancement
small bug with DOT output fixed
Better message in case of precondition failed
example for list_content
Doc: General content on list_labels/list_content switch Doc: reference updates Doc: shorter lines
Conflicts:
doc/testing_tools/boost_test_universal_macro.qbk
* topic/new-cla-cleaned:
Updated changelog
Allow some foreign token in between boost.test arguemnts for backward compatibility
Copyright updates
Doc: change log update
C++03 compatibility
Doc: updates for new cla
Parameters updates for new cla
Cleanup: utils namespace
New CLA cont.
Named parameters refactoring + tests
New CLA
- Adding the example and a visual output (DOT) and textual output
- Adding the legend
- SVGs are not rendered properly by quickbook, so the text contains a PNG
* topic/new-cla-cleaned:
Allow some foreign token in between boost.test arguemnts for backward compatibility
Copyright updates
Doc: change log update
C++03 compatibility
Doc: updates for new cla
Parameters updates for new cla
Cleanup: utils namespace
New CLA cont.
Named parameters refactoring + tests
New CLA
Conflicts:
doc/runtime_configuration/runtime_config_reference.qbk
- clarify the reference section
- emphasises the BOOST_<level>_THROW behaviour wrt. unexpected exceptions
- full example for API testing
- renaming cpp files
- adding examples
