boost 1.38 test suite in separate files
In the documentation from boost 1.38 (in the Unit Test Framework), there
is this example if having multiple test suits. (Example follows..)
My question is how can this be broken up and placed into different
files? For example, the files could be testSuite1.cpp, testSuite2.cpp,
and runTheseTestSuite.cpp.
#define BOOST_TEST_MODULE example
#include
AMDG Nu Ai Tang wrote:
In the documentation from boost 1.38 (in the Unit Test Framework), there is this example if having multiple test suits. (Example follows..) My question is how can this be broken up and placed into different files? For example, the files could be testSuite1.cpp, testSuite2.cpp, and runTheseTestSuite.cpp.
As long as you only define BOOST_TEST_MODULE in one translation unit it should be fine. In Christ, Steven Watanabe
Steven Watanabe
AMDG
Nu Ai Tang wrote:
In the documentation from boost 1.38 (in the Unit Test Framework), there is this example if having multiple test suits. (Example follows..) My question is how can this be broken up and placed into different files? For example, the files could be testSuite1.cpp, testSuite2.cpp, and runTheseTestSuite.cpp.
As long as you only define BOOST_TEST_MODULE in one translation unit it should be fine.
But! You can use single header variant of UTF in this case. You'll need to build a library. Gennadiy
AMDG Gennadiy Rozental wrote:
Steven Watanabe
writes: Nu Ai Tang wrote:
In the documentation from boost 1.38 (in the Unit Test Framework), there is this example if having multiple test suits. (Example follows..) My question is how can this be broken up and placed into different files? For example, the files could be testSuite1.cpp, testSuite2.cpp, and runTheseTestSuite.cpp.
As long as you only define BOOST_TEST_MODULE in one translation unit it should be fine.
But! You can use single header variant of UTF in this case. You'll need to build a library.
s/can/can't/? In Christ, Steven Watanabe
What library needs to be built?
static or dynamic. http://www.boost.org/doc/libs/1_39_0/libs/test/doc/html/utf/compilation.html
Also, how is the order of the test suite enforced?
It's not. Whatever order compiler/linker choose to execute static objects construction, that is the one you end up seeing. You can run specific test suites though and list them in particular order. Gennadiy
participants (4)
-
Gennadiy Rozental -
Nu Ai Tang -
Steven Watanabe -
tang10＠llnl.gov