« Return to Thread: [Boost.Test] [1.38] Automated test suie registration with muti-file-test-modules

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

by Gennadiy Rozental-2 :: Rate this Message:

Reply to Author | View in Thread

Greg Christopher <gchristopher <at> vmware.com> writes:

 >
 > Hi,
 > We are starting to expand the number of test modules and are having
 > some growing pains.
 >
 > Originally we were using the "single header" variant
 > included/unit_test.hpp file. Now we have switched
 > to linking to the dynamic version of the boost test library
 > and are including auto_unit_test.hpp.

Just unit_test.hpp is fine. Older name is deprecated.

 > We have been counting on the Test Tools to automatically register
 > suites and test cases. This still worked when we just included
 > unit_test.hpp (instead of included/unit_test.hpp).
 >
 > However with multiple test modules, init_unit_test_suite is being
 > defined in each module.

This should work as you expect. Please post simple example illustrating
your issues.

 > I would like multiple test suites, although the documentation for
 > this declares that there is a single global test suite.

You can have multiple test suite under the master test suite.

Gennadiy
_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

 « Return to Thread: [Boost.Test] [1.38] Automated test suie registration with muti-file-test-modules