Boost logo

Boost :

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.


Vinícius dos Santos Oliveira

Boost list run by bdawes at, gregod at, cpdaniel at, john at