cet-is » cetbuildtools

Please provide a working example of the problem. There may be a different solution.

The problem with Boost unit test suite is that there are too many solutions.
One if BOOST_TEST_MAIN is set, one if BOOST_TEST_DYN_LINK is set instead.
Since the documentation of cet_test does not say which one is supported when USE_BOOST_UNIT is set, I looked at the macro itself and it seems to define both.
Matter of fact, the first one, BOOST_TEST_MAIN, is ignored since a different COMPILE_DEFINITIONS is specified immediately after that (line 281).
Lines 280 and 281 should not coexist.
I redesigned my test to fit the BOOST_TEST_DYN_LINK model and now it works (no missing main() complaint, no empty test tree any more).
Still the spurious line 280 should be removed by cet_test (with no effect on any build).

Being my first attempt to use Boost unit tests, my goal was to put together a test, in any way I could.
The idea was that I could optionally specify from command line the random seed to be used.

So I was trying to use

boost::unit_test::test_suite* init_unit_test_suite( int argc, char* argv[] );

#include "boost/test/unit_test.hpp" 

boost::unit_test::test_suite* init_unit_test_suite( int argc, char* argv[] ) {
  std::cout << "Initializing tests..." << std::endl;
  return nullptr;
} // init_unit_test_suite()