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
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
std::cout or std::cerr.
This can be disabled by passing --no_color_ouput
(or just --no_color)
to the command line.
BOOST_AUTO_TEST_CASE_TEMPLATE
now accepts a sequence of types in an std::tuple
[clang] Fix [-Wc++11-narrowing] error
gcc
>= 7
stdcerr file
creation on shutdown
Windows.h include
to all-lowercase (MinGW)
std::tuple
typelists in BOOST_AUTO_TEST_CASE_TEMPLATE
print_helper_t<nullptr_t> under Clang
errors.hpp in Boost Test requires warning C4946 to be off
BOOST_AUTO_TEST_CASE_TEMPLATE
don't want typedef for list
begin
and end but not const_iterator
--log_sink=file
BOOST_TEST_GLOBAL_CONFIGURATION
(result report shutdown time)
BOOST_GLOBAL_FIXTURE is flagged
as deprecated and will be removed in a later version
BOOST_GLOBAL_FIXTURE. Please use
BOOST_TEST_GLOBAL_FIXTURE instead
(see below).
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.
BOOST_TEST check to comparing
a collection with respect to regular arrays. See this
section for more details.
random_shuffle
by more modern equivalents
BOOST_TEST_MESSAGE
in fixture constructor - invalid XML
BOOST_TEST_MESSAGE
generates incorrect output when used in BOOST_DATA_TEST_CASE
BOOST_TEST broken
with floating point relational operators
operator<< for a specific type.
success and
non-fatal error,
and defaults to general information.
BOOST_NO_EXCEPTIONS
typo making throw_exception
unusable under some circumstances
FE_* macros (unable to compile boost test library
on FPU-less arches) (reopened)
BOOST_AUTO_TEST_SUITE:
Generate unique names by using __COUNTER__
VERSION
nullptr issue)
:' 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.
per_element
and lexicographic
modifiers of BOOST_TEST can also be applied
to string comparison. See string
comparison for more details.
FE_* macros (unable to compile boost test library
on FPU-less arches)
BOOST_TEST() treat std::string
as a collection?
report_sink
description
--report_sink
parameter broken
--run_test
in Boost 1.62 does not accept test names which contain ':'
--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
--logger
and corresponding environment variable BOOST_TEST_LOGGER
for more details.
BOOST_TEST_DISABLE_ALT_STACK for
more details.
[bb10/qnx failures]
Build error
BOOST_DATA_TEST_CASE
abi::__cxa_demangle
on android
getchar() is defined as a macro in uClibc)
std::tuple
has broken
test_units
generated from test_case_gen
boost/test/impl/debug.ipp: Ignores return value from WaitForSingleObject
BOOST_DATA_TEST_CASE
BOOST_TEST(3u == (std::max)(0u, 3u)) fails
BOOST_DATA_TEST_CASE
fails to compile for 4D and higher dimensional grids
make as
top left dataset is not necessary anymore
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 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
<osreldate.h>
before testing __FreeBSD_version
(fixed in 1.59)
init_unit_test_suite
are incorrect when using path and whitespaces
ostream
precision after any Test macro (fixed in 1.59)
argv
if a paramter contains whitespace
BOOST_TEST( ..., per_element()
) comparison of vector<string>
BOOST_TEST() statements
BOOST_TEST(
0.0 ==
0.0 )
fails under C++11 (GCC and Clang)
BOOST_TEST(
..., per_element() ) erroneously
requires collections are comparable
BOOST_TEST generic assertion
color_output
list_content
BOOST_<level>_EQUAL_COLLECTION docs typo
_CrtSetReportFile
can be used to redirect memory leaks report
init_tests_func
BOOST_TEST_PASSPOINT macro
GT is GREAT!
vserver environment (duplicates ##3592)
SIGCHLD always
considered fatal error
BOOST_<level>_GT
description (duplicates ##3463)
BOOST_<level>_CLOSE_FRACTION
is incorrect
<boost/test/exception_safety.hpp> requires additional includes
BOOST_AUTO_EST_CASE
typos in docs
stderr
]]> incorrectly
BOOST_AUTO_TEST_CASE_TEMPLATE
config.hpp
BOOST_<level>_CLOSE_FRACTION
is not reflected into released documents
__FILE__ and __LINE__
at declaration point making it impossible to provide source file linking
using external test management tools
BOOST_REQUIRE_CLOSE
fails to compile with boost::multiprecision::cpp_dec_float_100
(duplicates ##11054)
enable_if/disable_if templates
const_string.hpp/const_string_test.cpp)
BOOST_<level>_GT
documentation bug (duplicates ##3463)
BOOST_TEST_DONT_PRINT_LOG_VALUE
sigaltstack
DS identifier
causes test failures in doc/examples/dataset_example*.cpp
BOOST_CHECK_EQUAL_COLLECTIONS:
can't control output operator (duplicates #9390)