The singleton is not robust to initialization in several translation units between
shared library with hidden visibility. Removing
Fixing tests accordingly.
The diagnostic is issued when compiled with GCC/clang flag -Wundef.
Although in case BOOST_CLANG is not defined, ie. is not a macro
and BOOST_CLANG identifier is considered to be zero, the #ifdef
directive makes the intention clearer.
* topic/12953-access-master_test_suite-in-datatest-cases:
Change log
Another example with different arity
Datasets based on std::initializer_list fixes
Delayed/lazy dataset construction
Handling sequences of size 0
# Conflicts:
# doc/closing_chapters/change_log.qbk
# test/Jamfile.v2
Since the previous changes, the elements of the std::initializer_list
get destroyed before the test tree initializes properly. The changes
are
- not relying on a moved std::initializer_list for storing the values
of the dataset. Those are moved to a std::vector instead if the
move constructor is noexcept as expected by std::vector,
- providing a template parameter pack for the same type of constructs
in place of the std::initializer_list
Some of the changes are also related to the fact that VS2013 does not
handle properly the std::initializer_list vs template parameter pack.
The dataset generators need to access runtime variables, which is
possible only after the test framework enters its setup.
The purpose of those changes is to instanciate the dataset and populate
the test tree during the initialization phase and not during the static
instanciation of the different test case:
- new delayed dataset type that is used for holding the parameters of a dataset
and its type. This dataset will be instanciated on demand (lazy construct)
- the test tree is now able to hold a generator until the init phase of the test
module. Once the init reached, the lazy datasets are instanciated and the test
tree populated with new tests.
- operations like zip do not require the size earlier than needed
The fact that the separator is empty for most of the short version
of the runtime parameters make it such that the parameter is considered
as another/next token.
- Skipped tests is not an error
- Handling of skipped tests
- Now printing when a test has been skipped because of the failed precondition
- More demonstrative test
- Unit test reproducing the precondition error issue
* topic/13528-crashes-with-report_sink:
Change log
Execute the callback cleaner also for stdout/stderr
Ensuring shutdown in all execution path
# Conflicts:
# doc/closing_chapters/change_log.qbk
- modifying a bit the API of the unit_test_log to retrieve the stream
- defining a test that checks after the framework executed that the streams
are correct
* topic/13181-collection-compare-missing-typename:
Change log and documentation update
Fixing VS compilation issues
forward_iterable: const_iterator infered by the type returned by begin
- Additional sanitizing logic for chars that appears on runtime filters
- Not sanitizing spaces anymore
- Remove leading and trailing spaces on test names
