BOOST_UNREACHABLE_RETURN creates several issues on
various MSVC compilers (manifest issue), curiously only
for the program monitor type of binaries. Making
a workaround for the time being.
- framework now does not shortcut the message when a skipped
tests is encountered
- framework messages are now at line "0" to avoid any further noise
in the messages when files in the framework are changed
- counting tests in case of disabled tests goes in the hierarchy
- counter class now has the ability to discard the enabled status
to count properly the children tests
- adding tests
- ensuring C++03 compatibility
* topic/GH-223-cannot-filter-template-test-cases:
Change log
Documentation updates
Normalizing test names accross several compilers
Sanitizing template test cases that contain ',' in their name
- subclassing cstring in order to be able to create an instance of cstring
without changing its signature: the code remains C++03/C++17 compatibile
even if boost.test is compiled with other options than the test module
- added casting and usage checks
- deduce_cstring rationale change
std::vector<bool>::const_iterator returns a temporary of a proxy class
while the value is needed for constructing the test case with parameters.
- added test reproducing the issue
On gcc and clang, add __attribute__((__format__)) checking to the report_error function.
Cast faulting addresses to uintptr_t for formatting as 0x%08lx - this won't work on LLP64, but Win64 uses SEH anyway.
Fix swapped si_code/si_addr (& si_band) format arguments.
Add missing %s to format diagnostic information.
- Check __GNUC__ major : format attribute was introduced sometime during gcc 2.8, so 3 definitely has it.
Same should apply for any compiler claiming GNUC compatibility
- Check that diagnostic information is not passed to format unescaped: If it is passed unescaped, the '%%' will be
condensed to a single '%' and the test will fail.
Check if SI_ASYNCIO and SI_MESGQ are defined as macros. This allows
to run tests on OpenBSD 6.5, where the macros are missing.
This is identical to patch-boost_test_impl_execution_monitor_ipp in
OpenBSD Ports, except that I added a comment.
* topic/GH-218-outstream-default-filename:
Change log
Master test suite name setup prior to all other setup
# Conflicts:
# doc/closing_chapters/change_log.qbk
This is a simple call to a global setting that can be performed
- in an idempotent manner
- prior to any other setup
Since some loggers rely on the master test suite (generation of the
output files), this setting should precede any other. In particular,
it should not be delayed until the user `init_unit_test` is called. A global object fits this purpose.
Fixes GH-209.
A new helper meta-function has been added to check if the type under
test is complete or not. Incomplete types cannot be used with
std::numeric_limits.
The newly added test cannot be run on pre C++11 because of the limited
BOOST_TEST support (unrelated to the std::numeric_limits issue).
Forward declarations for templates should also have the visibility right
Local static variables cannot have their visibility set and need to get out of the function scope.
- 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
Using arbitrary parameter pack of a template
class/struct to infer the list of types, instead
of restricting to `std::tuples`.
Filtering the mpl::sequences from this logic because
the parameter pack is filled with `mpl::na` on non-entries.
Failed and errored are exclusive in the JUnit sense.
Counting the number of total tests slightly differently.
Changing slightly the signature of unit_test_log_formatter::log_build_info to avoid a sticky
state when the function was called only once (happens for instance in JUNIT).
