3. You could redirect log and/or report streams. Put configure testcase as a first one in a module:
BOOST_AUTO_TEST_CASE( configure ) { boost::unit_test::results_reporter::set_stream( report ); boost::unit_test::unit_test_log::set_stream( log ); }
Eew! What if somebody decides to use the new random order feature of the test framework?
From results_reporter standpoint it doesn't matter. It only kicks in once all test cases are run.
I guess this is a usable workaround for now, but I really think there needs to be some capability to insert user code into the process in a more controlled fashion.
It may worth investigating, but keep in mind that it should be something that framework picks up automatically, but on the other doesn't require. These requirements usually contradict each other. Have any ideas? Gennadiy