...one of the most highly
regarded and expertly designed C++ library projects in the
world.
— Herb Sutter and Andrei
Alexandrescu, C++
Coding Standards
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
BOOST_TEST_PASSPOINT
macro
BOOST_<level>_GT
description (duplicates #3463)
BOOST_<level>_CLOSE_FRACTION
is incorrect
BOOST_AUTO_EST_CASE
typos in docs
]]>
incorrectly
BOOST_AUTO_TEST_CASE_TEMPLATE
__FILE__
and __LINE__
at declaration point making it impossible to provide source file linking
using external test management tools
const_string.hpp/const_string_test.cpp
)
BOOST_<level>_GT
documentation bug (duplicates #3463)
BOOST_TEST_DONT_PRINT_LOG_VALUE
DS
identifier
causes test failures in doc/examples/dataset_example*.cpp
BOOST_CHECK_EQUAL_COLLECTIONS
:
can't control output operator (duplicates #9390)