Re: [Boost-users] [Boost.Test] [1.38] Automated test suie registration with muti-file-test-modules

Subject: Re: [Boost-users] [Boost.Test] [1.38] Automated test suie registration with muti-file-test-modules
From: Greg Christopher (gchristopher_at_[hidden])
Date: 2009-07-01 14:20:55

Thanks for clearing this up...

> -----Original Message-----
> From: boost-users-bounces_at_[hidden] [mailto:boost-users-
> bounces_at_[hidden]] On Behalf Of Gennadiy Rozental
> Sent: Tuesday, June 23, 2009 6:27 PM
> To: boost-users_at_[hidden]
> Subject: Re: [Boost-users] [Boost.Test] [1.38] Automated test suie
> registration with muti-file-test-modules
> 
> Steven Watanabe <watanabesj <at> gmail.com> writes:
> 
> > Don't #define BOOST_TEST_MODULE in more than
> > one translation unit.
> 
> This is covered in docs I believe. BOOST_TEST_MODULE has similar effect
> as
> BOOST_TEST_MAIN, but also define the name of the master test suite

Since I don't really need to define the name of the master test suite, I will not use BOOST_TEST_MODULE.

As it turns out, that still does not yield a working example. I then have no init_unit_test_suite() defined. By messing around, I find that defining BOOST_AUTO_TEST_MAIN fixes the problem. Looks like I need to do that in some module? I thought that the main program would be pulled out of the library if I didn't provide one. While that may be true, init_unit_test_suite is not defined.

So may I assume that for a fully automated situation with multiple test modules, the right approach is simply to insure that BOOST_AUTO_TEST_MAIN is defined in one module?

Thanks again,
Greg