Boost C++ Libraries

...one of the most highly regarded and expertly designed C++ library projects in the world. Herb Sutter and Andrei Alexandrescu, C++ Coding Standards

Change log
PrevUpHomeNext

Boost.Test releases:

Boost.Test v3.15 / boost 1.79
New features
Bugfixes and feature requests
  1. #GH-268 Clang warning generated by dataset grid operation in C++20 mode
  2. #GH-272 Uninitialized memory in framework_init_observer_t
  3. #GH-284 Undefined behavior in basic_cstring<CharT>::trim_right
  4. #GH-297 BOOST_TEST_GLOBAL_FIXTURE documentation misleading
  5. #GH-305 boost test documentation tells users to file bugs with decommissioned Trac.
  6. #PR-286 fix uninitilized variable in framework_init_observer_t
  7. #PR-301 UB comparing unrelated pointers in priority_order
  8. #PR-275 Replace anonymous enum arity with static constexpr
  9. #PR-278 Use boost_test_print_type customization point in lazy_ostream
  10. #PR-281 Export execution_aborted exception to allow catching it from outside the DLL
Boost.Test v3.14 / boost 1.74
New features
  • Now able to detect when running under a debugger on macOS/iOS. When running under a debugger, Boost.Test does not try to catch system errors and the behaviour is the same as if the command line catch_system_error option was set to no. Thanks to Tom Hughes for this feature.
  • Adding support for Embarcadero C++ clang-based compilers, thanks to Edward Diener
Bugfixes and feature requests
  1. #GH-264 GCC suggest-override warnings
  2. #GH-269 Deprecated bind placeholders in tests
  3. #PR-142 Make under_debugger work on apple (iOS/macOS)
  4. #PR-266 Changes for Embarcadero C++ clang-based compilers
  5. #PR-267 Use macOS API only on macOS
Boost.Test v3.13 / boost 1.73
New features
  • It is now possible to combine tolerance indication, user message and collection comparison modifier in a single BOOST_TEST expression

    std::vector<double> v1 = f();
    std::vector<double> v2{1.1, 1.19};
    BOOST_TEST(v1 == v2, boost::test_tools::tolerance( 1e-3 ) << "comparison to ground truth failed" << boost::test_tools::per_element());
    
Bugfixes and feature requests
  1. #GH-173 Compare collections of floating point values with tolerance
  2. #GH-179 test_tools-test failed on some archs
  3. #GH-220 Support for cuda nvcc
  4. #GH-221 Coverity security issue (minor) (umask)
  5. #GH-235 Ugly GCC -Wattributes warnings that cannot be suppressed using included variant
  6. #GH-237 Clang-cl's -Wdelete-non-abstract-non-virtual-dtor triggered by test_case_gen
  7. #GH-241 warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  8. #GH-245 code coverity test defect
  9. #GH-246 Incorrect usage of BOOST_HEADER_DEPRECATED
  10. #GH-251 Context message are always printed if both HRF and Junit loggers are enabled
  11. #GH-253 Invalid XML log is generated by BOOST_AUTO_TEST_CASE_TEMPLATE when tests are skipped
  12. #GH-254 Console colors are not restored on Windows
  13. #GH-263 Windows: Header-only mode with multiple translation units requires BOOST_TEST_NO_LIB
  14. #PR-41 Fix: activate virtual destructors for all msvc versions
  15. #PR-114 Silence unreachable code warning in MSVC (/W4)
  16. #PR-187 enable BOOST_TEST with tolerance and user-message (through #GH-173)
  17. #PR-239 Fix unused variable warning in unit_test_main.ipp
  18. #PR-247 Use __linux__ instead of __linux
  19. #PR-252 Fix compilation issue due to deleted std::basic_ostream::operator<< from wchar_t
  20. #PR-259 Avoid deprecated bind placeholders in global namespace
  21. #PR-265 Suppress the unused parameter warning for root_test_unit_id
  22. #11107 A lot of warnings on MSVC due to protected destructor being non-virtual
  23. #12072 Lots of C4265 warnings in test when using Visual Studio 2015 (duplicates #11107)
Boost.Test v3.12 / boost 1.72
New features
  • Support for C++17 std::string_view has been added.
  • Better diagnostic on boost::exception and no rtti mode (thanks to Mikhail Pilin / #PR-234)
Bugfixes and feature requests
  1. #GH-206 compile-time disabled test not correctly handled by junit log
  2. #GH-217 Data test cases fail with bool initializer list
  3. #GH-223 Unable to filter test by name (-t, --run_test) if template type contains multiple parameters
  4. #GH-229 Random shuffle deprecated
  5. #PR-227 Add printf format checking attribute to report_error
  6. #PR-231 OpenBSD is missing SI_ASYNCIO and SI_MESGQ
  7. #PR-232 fix timeout in windows
  8. #PR-234 boost::diagnostic_information() works in no rtti mode
Boost.Test v3.11 / boost 1.71
New features
  • Now BOOST_TEST can be used to compare abstract types
Breaking changes
  • Marking more headers as deprecated: this might break some compilations depending on the warning policies.
Bugfixes and feature requests
  1. Fixing a small bug on named timers (Windows only). The bug is visible when several test modules are executed in parallel on the same machine.
  2. #GH-209 BOOST_TEST_CHECK can't compare abstract classes using gcc
  3. #GH-218 Default file name (for logger output files)
  4. #PR-219 Commented out unused argument name (stack_decorator::apply)
  5. #PR-224 Add BOOST_HEADER_DEPRECATED to deprecated headers
Boost.Test v3.10 / boost 1.70
New features
  • New documentation section about custom command line arguments
  • Custom datasets are not required to declare a inner type sample anymore
  • Boost.Test does not depend on Boost.Timer any more (which was pulling also Boost.Chrono and Boost.System as transitive dependencies).
  • Now Boost.Test raises an exception when the test case times-out on Windows. Prior to this release, times-out on Windows were not failing the test cases. Note that signaling is not available on Windows, and it is not possible to interrupt a test even in case of time out.
  • Time-out now applies to test-suites as well: a test-suite is marked as timed-out if it exceeds the allocated time. The test units that were not executed at the time-point of the time-out are skipped.
  • It is now possible to pass several values for the same context via the tool BOOST_TEST_CONTEXT.
  • A new macro BOOST_TEST_INFO_SCOPE let define a context for the current scope in a sticky way.
  • It is now possible to use floating point comparison without being required to cast both operands to floating point types. Now Boost.Test uses floating point comparisons for expressions such as

    BOOST_TEST(3.0001 == 3);
    

    See this section for more information.

Breaking changes
  • Boost.Test minimal.hpp is now showing a deprecation warning. minimal.hpp has been deprecated for a long time already, and will be removed in the near future. Please switch to eg. the header only variable of Boost.Test. Tests using minimal.hpp can readily be converted to the header variant. For instance, the following code:

    #include <boost/test/minimal.hpp>
    int test_main( int, char *[] )
    {
      ...
    }
    

    may be rewritten as:

    #include <boost/test/included/unit_test.hpp>
    BOOST_AUTO_TEST_CASE(test_main)
    {
      ...
    }
    
  • The floating point comparison behavior change may use this type of comparison while previously using straight relational operator comparison. In particular this may causes new warnings.
  • the member function boost::unit_test::unit_test_log_formatter::log_build_info has slightly changed to accept an additional boolean argument. If you have a custom logger, you will need to update its signature.
Bugfixes and feature requests
  1. #GH-133 Timeout effect on Windows
  2. #GH-138 expected_failures doesn't work for BOOST_DATA_TEST_CASE
  3. #GH-141 Support for Boost.MP11 and Boost.Hana type lists
  4. #GH-157 Test name should handle const-volatile specifiers
  5. #GH-160 suppress -Wformat-overflow when optimization is enabled on GCC 8.2.0
  6. #GH-174 UBSAN identified a problem at exit time by gcc-8 only
  7. #GH-176 [snippet_dataset1_3] seems to be broken
  8. #GH-177 boost_check_equal-str-test failed on llvm
  9. #GH-180 Unreachable code warning on MSVC builds in test matrix
  10. #GH-181 doc_example22 (and 23) are expected to fail, but do not on clang with release variant builds
  11. #GH-194 master_test_suite declared twice
  12. #GH-196 junit report: test error is also reported as failure
  13. #GH-198 Support BOOST_UNIT_TEST_FRAMEWORK_DYN_LINK et al
  14. #GH-199 Runtime type_mismatch after upgrade to 1.69
  15. #GH-202 boost/timer.hpp is deprecated
  16. #GH-203 Test cases with datasets and fixtures don't support flexible fixture interface
  17. #GH-204 Feature Request: Allow specifying timeouts for test cases with datasests.
  18. #GH-208 Incorrect handling of timed-tests on Windows
  19. #GH-211 windows.h should be lower case
  20. #GH-212 Comment ar parameter of assertion_result to avoid warning
  21. #GH-213 BOOST_SYMBOL_VISIBLE cannot be used for enums with Sun Studio
  22. #PR-171 Correct library name in test runner help screen
  23. #PR-172 Check for non-used variables when NDEBUG is defined
  24. #PR-182 fix use of bind1st in example 12
  25. #PR-183 remove superfluous semicolon in example 04
  26. #PR-184 fix example to use the correct variable and avoid unused variable warning
  27. #PR-185 Added CI framework
  28. #PR-190 fix warning on gcc-7.3 in cygwin claiming master_test_suite is declared differently
  29. #PR-195 Fix MinGW compilation problems
  30. #PR-197 Feature Request: BOOST_TEST_CONTEXT that doesn't require introducing a new scope with braces
  31. #PR-205 Fix MinGW vsnprintf compile errors and warnings
  32. #PR-214 Fixes an issue with sun_cc lacking the __global attribute for enums
  33. #7397 Boost.Test, since boost 1.48 is using the deprecated Boost.Timer class (solved via #GH-202)
  34. #9434 error: namespace boost::timer {} re-declared as different kind of symbol (solved via #GH-202)
  35. #13106 libs/test/tools/console_test_runner does not compile
  36. #13418 Request: allow general typelist types in BOOST_AUTO_TEST_CASE_TEMPLATE()
Boost.Test v3.9 / boost 1.69
New features
  • Official support of header-only variant of Boost.Test with multiple translation units. This feature was available but needed to be properly documented (here and here).
  • It is now possible to manually add a test case by specifying its name, with BOOST_TEST_CASE_NAME
  • Better logging of messages in boost::exception
Bugfixes and feature requests
  1. #GH-149 Setting color_output=no does not disable the output of color format codes
  2. #GH-150 Some headers fail to compile independently
  3. #GH-156 close_at_tolerance always returns false for comparisons of infinity
  4. #GH-158 Detecting boost_test_print_type does not work when testing a type with an explicit conversion to bool
  5. #GH-163 Significant start slowdown on MSVC x64/Debug after upgrade to v1.68.0
  6. #PR-147 Catch block for boost::exception appears after std::exception in execution_monitor::execute()
  7. #PR-148 Colored output contradiction
  8. #PR-151 Fix warning: BOOST_CLANG is not defined, evaluates to 0
  9. #PR-154 When specifying --color_output=no, don't output color codes
  10. #PR-161 add a self-containment test
  11. #13380 data-driven tests' join operator + corrupts first column (duplicates #12216)
  12. #13625 Boost.test fail to compile with -Werror=missing-declarations on some architectures
  13. #13637 Fix for Bug #12597 causes a problem with BOOST_TEST_CASE
Boost.Test v3.8 / boost 1.68
New features
  • The tests generated from a dataset are now instantiated during the framework setup. This let the dataset generator access the argc and argv of the master test suite. For indicating a dataset that should be instantiated in a delayed manner, a new data::make_delayed helper has been introduced.
  • It is now possible to create a dataset with data::make, with variable number of arguments. As the datasets are monomorphic, it should be possible to cast all elements to the first element type.
Breaking changes
  • the master_test_suite_t is not copyable anymore.
  • As datasets can now be delayed, it might be that additional copies of the dataset arguments are performed. This is especially the case for datasets created out of an std::initializer_list.
Bugfixes and feature requests
  1. #PR-143 Fix exception_api.run-fail.cpp doc example
  2. #PR-145 Fix build of library on recent Cygwin editions
  3. #12095 disabling test with precondition leads to error
  4. #12953 access to master_test_suite().{argc, argv}
  5. #13504 [Boost::Test] short form of catch_system_errors not working
  6. #13525 Boost Test 1.67.0: Compilation error with GCC 4.6.3
  7. #13528 Boost Test 1.67 crashes when the --report_sink command-line parameter is used
Boost.Test v3.7 / boost 1.67
Breaking changes
  • Now colour is on by default for the output streams that are either std::cout or std::cerr. This can be disabled by passing --no_color_ouput (or just --no_color) to the command line.
  • Adding test cases with the same name to the same test suite is reported as an error. This impacts template and parametrized test cases, as well as manually registered tests. Make sure you have no duplicate names.
New features
  • Colour output on Windows
  • Improved and clearer command line help
  • BOOST_AUTO_TEST_CASE_TEMPLATE now accepts a sequence of types in an std::tuple
Bugfixes and feature requests
  1. #PR-112 Deliberate-failure tests shouldn't be optimized
  2. #PR-118 Update VxWorks support
  3. #PR-118 [clang] Fix [-Wc++11-narrowing] error
  4. #PR-121 fix compiler warning
  5. #PR-122 Fix some fallthrough warnings with gcc >= 7
  6. #PR-125 Prevent 2 unused parameter warnings
  7. #PR-127 Silence 'unused variable' warning
  8. #PR-134 Fix stdcerr file creation on shutdown
  9. #PR-136 Change Windows.h include to all-lowercase (MinGW)
  10. #12092 Request: allow std::tuple typelists in BOOST_AUTO_TEST_CASE_TEMPLATE
  11. #12596 Sanitize metacharacters in test names
  12. #12597 Report tests with clashing names
  13. #12969 Problem linking print_helper_t<nullptr_t> under Clang
  14. #13058 errors.hpp in Boost Test requires warning C4946 to be off
  15. #13149 Dependency decorators on parent suites
  16. #13170 BOOST_AUTO_TEST_CASE_TEMPLATE don't want typedef for list
  17. #13181 Boost test can't compare classes which have begin and end but not const_iterator
  18. #13371 Use-after-free with --log_sink=file
  19. #13387 Test header fails to compile
  20. #13398 Log format JUNIT generates invalid XML files
  21. #13407 Boost.Test appears to crash under Cygwin
  22. #13435 BOOST_TEST_GLOBAL_CONFIGURATION (result report shutdown time)
  23. #13443 Boost.Test data driven test fails to compile when number of samples greater than 9
Boost.Test v3.6 / boost 1.65
Breaking changes
New features
  • VS2017 / C++17 compatibility (thanks to Daniela Engert)
  • Deprecating BOOST_GLOBAL_FIXTURE in favor of BOOST_TEST_GLOBAL_FIXTURE and BOOST_TEST_GLOBAL_CONFIGURATION. This helps separating the logic of the fixtures associated to the master test suite, from the one used for setting up the logging and reporting facility, and results in a general cleaner design.
  • It is possible to use now the BOOST_TEST check to comparing a collection with respect to regular arrays. See this section for more details.
Bugfixes and feature requests
  1. #PR-106 replace deprecated binders and adapters, and random_shuffle by more modern equivalents
  2. #5282 Test fixtures do not support virtual inheritance
  3. #5563 using a test macro in a global fixture crashes Boost.Test
  4. #11471 array is a sequence
  5. #11962 BOOST_TEST_MESSAGE in fixture constructor - invalid XML
  6. #12228 Some test headers fail to compile independently
  7. #12631 BOOST_TEST_MESSAGE generates incorrect output when used in BOOST_DATA_TEST_CASE
  8. #13011 BOOST_TEST broken with floating point relational operators
Boost.Test v3.5 / boost 1.64
New features
  • Now Boost.Test provides customization points for logging user defined types: this solution is less intrusive than forcing the definition of operator<< for a specific type.
  • JUnit output format can now have a log-level set between success and non-fatal error, and defaults to general information.
  • JUnit output format is now more efficient in case a lot of checks are done in a test module.
Bugfixes and feature requests
  1. #PR-107 BOOST_NO_EXCEPTIONS typo making throw_exception unusable under some circumstances
  2. #PR-108 Change capital variable names to lowercase
  3. #11756 boost.Test: non standards compliant use of FE_* macros (unable to compile boost test library on FPU-less arches) (reopened)
  4. #12540 Provide customization point for printing types in tests
  5. #12712 BOOST_AUTO_TEST_SUITE: Generate unique names by using __COUNTER__
  6. #12748 Boost.Test defines a variable called VERSION
  7. #12778 Boost.Test is broken against left shift operator in certain cases (nullptr issue)
Boost.Test v3.4 / boost 1.63
Breaking changes
  1. Now colons that appear in test case names are replaced with underscores. This affect mainly the template/typed test cases. The change is needed since the colon ':' is interpreted as a filter separators since 1.62, and it is otherwise not possible to execute the tests reported by --list_content. See #12531 for more details.
New features
Bugfixes and feature requests
  1. #PR-103 Syntactic change silences latest gcc warnings
  2. #PR-105 Fix unused parameter warnings/errors with gcc 6
  3. #11756 boost.Test: non standards compliant use of FE_* macros (unable to compile boost test library on FPU-less arches)
  4. #11907 Why does BOOST_TEST() treat std::string as a collection?
  5. #12339 Propose users given way to disable blink in colour output
  6. #12506 typo in Boost.test report_sink description
  7. #12507 Boost.test --report_sink parameter broken
  8. #12530 No way to find out Boost.Test version without running any tests
  9. #12531 --run_test in Boost 1.62 does not accept test names which contain ':'
Boost.Test v3.3 / boost 1.62
New features
  • Boost.Test now treats each sample of a dataset test case as being a uniquely named test case under the same test suite, which enables the (re)run of one particular sample from the command line interface. See here for more details,
  • Boost.Test learned to interpret ':' as a separator for the test filters: the string passed to --run_test generates tokens as if --run_test has been repeated, which enables the set up of several test filters through the associated environment variable BOOST_TEST_RUN_FILTERS
  • the Unit Test Framework learned to log the messages in the xUnit/JUNIT log format. See here for more details.
  • the Unit Test Framework learned to have several loggers at the same time, each of which with their own log level and log sink. See the associated command line switch --logger and corresponding environment variable BOOST_TEST_LOGGER for more details.
  • loggers are now able to indicate their default output stream and log level.
Bugfixes and feature requests
  1. #PR-81 Possibility to remove the support of the alternative stack at compilation time. See BOOST_TEST_DISABLE_ALT_STACK for more details.
  2. #8707 Provide Standard xUnit XML Output from Boost Test
  3. #8834 Boost Test should be able to generate report in both XML and HRF together
  4. #11128 [bb10/qnx failures] Build error
  5. #11845 Ability to generate the unique and stable test name for every data set in BOOST_DATA_TEST_CASE
  6. #11859 Wrong handling of "," in Run-Parameters
  7. #12024 boost test depends on nonexisting abi::__cxa_demangle on android
  8. #12093 Boost 1.60.0: Build fails (gcc 4.6)
  9. #12103 Fix for gcc bug 58952 (getchar() is defined as a macro in uClibc)
  10. #12224 Crash on MSVC with RTTI disabled
  11. #12241 Data-driven testing over a range of std::tuple has broken
  12. #12257 Incorrect line numbers in test_units generated from test_case_gen
  13. #12378 Compilation errors with clang 3.8
Boost.Test v3.2 / boost 1.61
New features
  • now datasets support any arity, using the variadic template support of the compiler.
  • now datasets support fixtures through BOOST_DATA_TEST_CASE_F, see here for more details
  • now datasets honors move semantics of the types used for samples
Bugfixes and feature requests
  1. #6767 Use of namespace qualifier with floating point exception functions breaks if they are macros
  2. #8905 boost/test/impl/debug.ipp: Ignores return value from WaitForSingleObject
  3. #9443 Runtime parameter Random seed for random order of test cases not respected correctly
  4. #11854 Add fixture support in BOOST_DATA_TEST_CASE
  5. #11887 BOOST_TEST(3u == (std::max)(0u, 3u)) fails
  6. #11889 BOOST_DATA_TEST_CASE fails to compile for 4D and higher dimensional grids
  7. #11983 Boost Test XML Report contains unescaped XML characters
Boost.Test v3.1 / boost 1.60
New major features
  • improved API for datasets
    • it is now possible to use initializer lists
    • the use of make as top left dataset is not necessary anymore
  • improved command line interface
    • clearer help commands
    • now proposes closest matching command in case of ambiguity
    • reports invalid or ambiguous parameters: this might break existing calls when user defined commands are provided to the test module. The following calling convention should be adopted:

      • if the test module uses user supplied commands, those should be passed after an empty token --
      • all boost.test related commands should be passed before --, if any

      Example: the call

      test_module --user-arg1=xy --log_level=test_suite
      

      should be rewritten to

      test_module --log_level=test_suite -- --user-arg1=xy
      
Bugfixes and feature requests
  1. #3384 Double-quoted arguments including spaces are divided by Boost.Test.
  2. #3897 Test framework does not include <osreldate.h> before testing __FreeBSD_version (fixed in 1.59)
  3. #6032 Program options within init_unit_test_suite are incorrect when using path and whitespaces
  4. #6859 Boost.Test eats away last empty command line parameter
  5. #7257 Boost.Test alters and does not restore ostream precision after any Test macro (fixed in 1.59)
  6. #9228 Patch to make Boost.Test work with RTTI disabled (fixed in 1.59)
  7. #10317 boost::test corrupts contents of argv if a paramter contains whitespace
  8. #11279 invalid parameters should be reported
  9. #11478 Boost Test Exception Assert Failure has poor message
  10. #11571 Can't compile BOOST_TEST( ..., per_element() ) comparison of vector<string>
  11. #11623 Clang rejects some simple BOOST_TEST() statements
  12. #11624 BOOST_TEST( 0.0 == 0.0 ) fails under C++11 (GCC and Clang)
  13. #11625 BOOST_TEST( ..., per_element() ) erroneously requires collections are comparable
Boost.Test v3 / boost 1.59
New major features
Bugfixes and feature requests
  1. #2018 Error in the documentation chapter "Runtime parameters reference"
  2. #2450 equations in Floating-point comparison algorithms html are not rendered properly
  3. #2600 Unit Test Framework - missed documentation
  4. #2717 BOOST_<level>_EQUAL_COLLECTION docs typo
  5. #2759 Typos in test new-year-resolution.html
  6. #3182 _CrtSetReportFile can be used to redirect memory leaks report
  7. #3316 Access violation when trying to log from init_tests_func
  8. #3392 Boost::Test: Wrong contents for documentation of the BOOST_TEST_PASSPOINT macro
  9. #3402 Invalid define name in documentation (duplicates ##2717)
  10. #3445 incorrect link in the docs
  11. #3463 GT is GREAT!
  12. #3542 Bug in documentation of detect_memory_leak parameter (duplicates ##2018)
  13. #3481 Boost Testing doesn't work under Sun Solaris Containers (duplicates ##3592)
  14. #3495 Boost::Test enters endless loop when running in vserver environment (duplicates ##3592)
  15. #3592 under_debugger() goes into infinite loop
  16. #3595 Typo (duplicates ##2759)
  17. #3623 Boost Test Typo (duplicates ##2759)
  18. #3664 SIGCHLD always considered fatal error
  19. #3784 Documentation errors in Execution Monitor Compilation
  20. #3785 Documentation errors in Program Execution Monitor implementation
  21. #3811 global namespace pollution
  22. #3834 doc: probably incorrect HTML rendering (duplicates ##2450)
  23. #3896 erroneous documentation in boost test command line parameter description
  24. #3932 Error in BOOST_<level>_GT description (duplicates ##3463)
  25. #3938 doc: incorrect macro name (duplicates ##2759)
  26. #3964 Documentation for BOOST_<level>_CLOSE_FRACTION is incorrect
  27. #3978 Failed to completely redirect TestLog to file, bugfix appended
  28. #3979 <boost/test/exception_safety.hpp> requires additional includes
  29. #4161 spelling mistakes...
  30. #4275 Documentation error Boost.Test (duplicates ##2717)
  31. #4389 Enable boost_test to run specific tests with any required dependent tests.
  32. #4434 BOOST_AUTO_EST_CASE typos in docs
  33. #4587 Broken link in website
  34. #4806 Invalid link (examples not showing up in documentation)
  35. #4911 ENH: boost.test output the exception real type name.
  36. #4923 Missing semicolon in documentation example
  37. #4924 Minor typo in Boost::Test docs
  38. #4982 Boost.Test has misspelled Gennadiy Rozental e-mail address
  39. #5008 Boost.Test does not do check-pointing of entry/exit of test cases
  40. #5036 Boost.Test VC memory leak report should direct to stderr
  41. #5262 Run tests by name utility doesn't support negation
  42. #5374 Errors from Boost.Test are no more shown in the Error list in VS2010
  43. #5412 XML formatter in test library processes strings with subsequences ]]> incorrectly
  44. #5563 using a test macro in a global fixture crashes Boost.Test
  45. #5582 There is a memory leak in the BOOST_AUTO_TEST_CASE_TEMPLATE
  46. #5599 boost::test documentation gives poor instruction
  47. #5718 broken link to unit testing framework examples
  48. #5729 Missing static_cast in fpt_limits
  49. #5870 The warning stack is not maintained
  50. #5972 Support program option to only dump the test-tree in text to output stream
  51. #6002 Failed to completely redirect TestLog to file (duplicates)
  52. #6071 Boost Test (Boost 1.46.0) GCC 4.6.1 error: ambiguous overload for ‘operator[]’
  53. #6074 warnings-as-errors not usable with Boost.test in release mode
  54. #6161 SunOS: bad putenv declaration (duplicates #6766)
  55. #6766 incorrect declaration for putenv in config.hpp
  56. #6712 Eliminate warnings with GCC
  57. #6748 Link in the documentation points to wrong page
  58. #7046 Output full error message, not just 512 chars
  59. #7136 Correct documentation for BOOST_<level>_CLOSE_FRACTION is not reflected into released documents
  60. #7410 Test Units (Cases and Suites) in Boost.Test do not capture __FILE__ and __LINE__ at declaration point making it impossible to provide source file linking using external test management tools
  61. #7894 Boost.Test documentation contains no linking instructions
  62. #8201 Broken link in document
  63. #8272 BOOST_REQUIRE_CLOSE fails to compile with boost::multiprecision::cpp_dec_float_100 (duplicates ##11054)
  64. #8467 Incorrect link in document (duplicates ##6748)
  65. #8679 Boost.Test pollutes boost namespace with it's own enable_if/disable_if templates
  66. #8862 Boost.Test typo in documentation
  67. #8895 English error in test collection comparison
  68. #9179 Documentation: broken link (unable to find const_string.hpp/const_string_test.cpp)
  69. #9272 boost::test BOOST_<level>_GT documentation bug (duplicates ##3463)
  70. #9390 Incomplete BOOST_TEST_DONT_PRINT_LOG_VALUE
  71. #9409 Some source code examples are missing
  72. #9537 const_string_test example fails
  73. #9539 Floating-point comparison algorithms aren't formatted correctly
  74. #9581 Squassabia reference link gives 404 not found
  75. #9960 Warnings on Clang
  76. #10256 [boost test] - issue: sigaltstack
  77. #10318 Minor documentation fix
  78. #10394 Broken links in Boost Test documentation
  79. #10888 Assertion failures don't show up in the errors pane in VS 2010, VS 2012 or VS 2013 (duplicates)
  80. #11054 Floating-point comparison of multiprecision values fails if expression template is on
  81. #11347 DS identifier causes test failures in doc/examples/dataset_example*.cpp
  82. #11358 Boost.Test v3 warning could helpfully be suppressed.
  83. #11359 BOOST_CHECK_EQUAL_COLLECTIONS: can't control output operator (duplicates #9390)
  84. #11425 use-of-uninitialized-value (obsolete)

PrevUpHomeNext