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.
- adding tests for custom command line argument passing
- using command line argument in global fixtures and raising strong errors
- using command line argument in init function and describing the errors
- using command line argument dataset test cases and describing the errors
- removing sample totally from all the examples
* topic/PR-185-CI-framework:
Change log
Disabling cppcheck on Travis
Indicating UBSAN for clang build
Adjusting the UBSan options
Added CI framework - travis with valgrind, cppcheck, ubsan, codecov, covscan (future) - appveyor with MSVC 2010 through 2017, cygwin 32/64, mingw 32/64 - README, LICENSE, etc. - Fixed example Jamfile to build examples based on C++ features
* doc/various-updates-cleanups:
Nicer change log
Typo
Change log PR-190
Repointing former SGI links
Correcting BOOST_TEST messages in the scope of the Contexts documentation
Fixing floating point dead link
Removing the need for samples from datasets
Change log with TOC
* topic/GH-202-boost-timer-deprecation:
Change log
Documentation updates
Adding the support for skipped test units/suites in the reporter and formatters
<boost/timer.hpp> removal and time-out for suites and major refactoring
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.
It is now possible to compare a type that is tolerance based together
with a type that is not necessarily tolerance based but still
arithmetic.
Doc update and tests.
- Functions being optimized: making functions having side-effects to prevent
optimizations to remove the calls.
- UB (divide by zero) is compiler implementation specific and does not raise
an exception on CLANG, rewrite the test to serve the purpose of the
boost.test macro.
