[Please do not mail me a copy of your followup] boost-users@lists.boost.org spake the secret code <87ipml2c8u.fsf@avasys.jp> thusly:
Boost.Test already support three "symbols":
BOOST_REQUIRE_* BOOST_CHECK_* BOOST_WARN_*
What you're seems to be implying is that BOOST_WARN_* is a bad idea.
Not just BOOST_WARN_*, but also BOOST_CHECK_* since they keep executing a failed test case. If you keep executing a test case that's already failed, it is highly likely in C++ that the test runner will simply crash.
I disagree, because there are "failure" modes that are not release critical.
Segregate them into a separate test project, change the warnings to failures and setup a separate CI build for them. -- "The Direct3D Graphics Pipeline" -- DirectX 9 version available for download http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/ Legalize Adulthood! http://legalizeadulthood.wordpress.com