[boost] [test] Not using Boost.Test for an official Boost library

Subject: [boost] [test] Not using Boost.Test for an official Boost library
From: Vinícius dos Santos Oliveira (vini.ipsmaker_at_[hidden])
Date: 2016-03-21 15:47:23

Hi list,

I'd like to know if it's mandatory to use Boost.Test if you intend to
contribute a library to Boost.

After facing an issue trying to enable compiler santizers on my tests[1]
for long enough, I'd like to use a different test library.

According to a survey done by Niall concerning new libs[2], everybody
avoids Boost.Test, favouring assert/static_assert.

I've been interested in using Catch[3], which is header-only and can be
embedded, posing no problem to users (it'd be transparent). I've seen
Boost.AFIO (which is not an official Boost library) already uses it.

I've seen lightweight_test is also used within Boost[4].

If Boost.Test ever fix its integration problem with compiler sanitizers[1],
I'd have no problem migrating everything back again to Boost.Test. However,
it's more important for me to have this issue solved now so I can jump to
the next task (valgrind and fuzz testing).

I've also seen that some header-only libraries use a different build system
for the test target[5] and using a header-only test library would be a
lesser demand that should be okay.

[1] https://svn.boost.org/trac/boost/ticket/11425
[2]
https://raw.githubusercontent.com/boostcon/cppnow_presentations_2015/master/files/A-review-of-Cxx-11-14-only-Boost-libraries-Fiber-AFIO-DI-and-APIBind.pdf
[3] https://github.com/philsquared/Catch
[4]
http://www.boost.org/doc/libs/1_60_0/libs/core/doc/html/core/lightweight_test.html
[5]
https://github.com/boostorg/hana/blob/63c5f87dfdadd07e496cefefc63c3ea9968d3140/CMakeLists.txt#L159

-- 
Vinícius dos Santos Oliveira
https://vinipsmaker.github.io/