BOOST_TEST_MESSAGE in fixture constructor - invalid XML

[nigels.com@…]

I came across an issue with our global fixture using BOOST_TEST_MESSAGE. The resulting XML file in --output_format=XML --log_level=all mode has the message, but not wrapped in the

<TestLog> ... </TestLog>

scope. In turn xsltproc would break on this, trying to convert to JUnit. I think it would be better for the BOOST_TEST_MESSAGE to either be silently dropped, or perhaps buffered, or TestLog XML tag should be forced.

Using boost 1.59.0 here.

[Raffi Enficiaud]

Merged to master rev 6a3a616

[Raffi Enficiaud]

Sorry wrong ticket :)

[nigels.com@…]

Dang! :-)

[Raffi Enficiaud]

The problem here is that global fixture are convenient for changing the logger at runtime, so they must be executed before the logger starts.

I am thinking of a fix. Do you have a snippet?

[Raffi Enficiaud]

Digging deeper: this is related to #5563

[Raffi Enficiaud]

Hi,

I just pushed a fix on the develop branch (rev ea9d9b9a8ea3f9aceb71cce41d48c820f05b2fdc) that addresses the issue by adding a dedicated macro for global fixtures BOOST_TEST_GLOBAL_FIXTURE and decouples it from the global initialization (that now goes to BOOST_TEST_GLOBAL_INITIALIZATION).

The global init cannot receive any logs, while the global fixture can. It should solve your issue, and it would be nice if you give a try.

[Raffi Enficiaud]

In master, rev 3d13638c412ac357f178e99a99bf44dfd756c057