Raffi Enficiaud — Tue, 13 Sep 2016 12:25:17 GMT

If you want to have that output in the final XML, I suggest you using BOOST_TEST_MESSAGE instead (see documentation here).

This is also what eg. Google test proposes.

In any case, if you mess with the logger output stream, then the output stream is likely to be invalid.

Tue, 13 Sep 2016 12:51:04 GMT

I'm the author of the unit test runner in ReSharper C++, so I'm actually providing an interface to Boost.Test.

We can't use XML log format with Google Test, since it's not streaming, so we use the console reporter which is fairly easy to parse. In Boost.Test the XML reporter is streaming, but not flushing, so we use it with the stderr sink - the only problem is unescaped user output which the standard XML reader fails to parse, and we've got several user requests about this problem.

Again, please take a look at how Catch handles that - it intercepts all user output and escapes it (e.g. in the JUnit reporter). Ideally I'd like Boost.Test to adopt the same approach.

Boost C++ Libraries: Ticket #12452: XML log can contain unescaped characters from test output