- new macros:
BOOST_TEST_GLOBAL_FIXTURE: for global "real" fixtures
BOOST_TEST_GLOBAL_CONFIGURATION: for global configuration of observers.
- deprecating BOOST_GLOBAL_FIXTURE. BOOST_GLOBAL_FIXTURE and BOOST_TEST_GLOBAL_CONFIGURATION are currently
fully equivalent, the former being confusing in term of scope/role is deprecated
- SFINAE detection for a setup/teardown function within the fixture class
- Attaching global fixture to the main or master test unit being executed, exactly as other fixtures. Global fixtures
via BOOST_TEST_GLOBAL_FIXTURE registers themselves in a particular field of the framework and are attached each time
the framework executes the tests, such that we can run the framework on another test root and still benefit from the
global fixtures. The global fixtures are appended to already existing fixtures (in case the master test suite is not
the root of the current execution tree).
- Checking that the framework setup is not failing for running the test
- RAII class for restoring the global fixtures
- Tests on the setup/teardown detection
- Tests on global fixtures and baseline
- Fixing several logging issues
Some additional refactoring
- renaming m_curr_test_case to m_curr_test_unit
- function for providing the current test unit (and not only the current test case)
- for output_stream comparison: stops properly if the reference stream is shorter than the current one,
initialises the read char correctly to 0 and prints a proper ~ at the mismatch location
- Make JUnit logger discard the log levels to log all events
- Currently JUnit discards the file directory where the assertion is being logged
- Uses tree visitation at the end of the test suite in order to generate the log file
* develop: (62 commits)
Fixing tests on GCCs
Fixing test on GCCs
Fixing the tests of this file for GCCs
Fix collection test on Gccs
Adding support for C++11 to old gcc compilers as well Fixing issues with arrays
Fixing counter for r-value ref supported but std::vector still lacking the proper constructor
Once for all the "Mismatch at" instead of "Mismatch in" for every type of collection
silence a warning in gcc 4.5
Revert "introduce fpc::tolerance_based to be used instead of if_floating_point. This should allow us to extend tolerance based comparisons t omore types"
Revert "introduce fpc::tolerance_based to be used instead of is_floating_point. This should allow us to extend tolerance based comparisons t omore types"
introduce fpc::tolerance_based to be used instead of is_floating_point. This should allow us to extend tolerance based comparisons t omore types
introduce fpc::tolerance_based to be used instead of if_floating_point. This should allow us to extend tolerance based comparisons t omore types
remove executable from header
remove executable form header
fix MSVC-12 tests
ENABLE new test tools fix few leftovers from implementation of new FPV comparisons restore test case in test_fp_comparisons.cpp
test to clear the error on CrystaX runners
some doc
const of the elements of the table
Trying to fix the array problem on Clang 3.4
...
Conflicts:
doc/examples.qbk
doc/test_organization/decorators.qbk
doc/test_organization/parametric_test_case_generation.qbk
include/boost/test/data/monomorphic/fwd.hpp
include/boost/test/data/monomorphic/generators/random.hpp
include/boost/test/data/monomorphic/singleton.hpp
include/boost/test/tools/floating_point_comparison.hpp
test/test_files/test_tools_test.pattern
on VC++8.0. I don't know why Microsoft thinks it's a good idea to call this an error,
but they do. I also don't know why people insist on checking out files on Windows and
copying them to a unix system to check them in (which will cause exactly this problem)
[SVN r26746]
eliminated need for ::instance()
eliminated need for << end and ...END macro
straitend interface between log and formatters
change compiler like formatter name
minimized unit_test_log interface and reworked to use explicit calls
[SVN r26720]
