On 21.02.19 02:15, Klaim - Joël Lamotte via Boost-users wrote:

On Wed, 20 Feb 2019 at 23:59, Raffi Enficiaud via Boost-users wrote:

...

As of today, virtually nothing has been done to make the library thread safe. It is not impossible but it would require quite a chunk of work.

Raffi

As a user data point: Both in the company I work for and in some other projects I work on, I had to resort to use GTest instead of either Boost.Test or Catch2 because of the lack of thread-safe checking api. Apparently Catch2 author now plan to implement thread-safe assertions.

Just so you know that it's an important feature for a lot of projects (but I understand it's not necessarilly easy to provide).

A. Joël Lamotte

Thanks for the feedback. I know it is an important feature, and it is there for a long time :) (see eg. https://svn.boost.org/trac10/ticket/3484). What would be possible at low/moderate cost would be to have thread safety while inside a test case, where assertions and messages can come from different threads. Would that make you use boost.test? In a second step, I can work on making the framework thread-safe such that we can enable parallel test-case execution. This would be more tricky because it involves more components. I suggest we start easy. Raffi