From: Sohail Somani (s.somani_at_[hidden])
Date: 2007-04-08 11:37:20
This probably belongs on the users list, but I think you treat tests as the same way you treat your code. Would you have all your code in one file? I usually split up my tests the same way I split up my code.
So the structure might look like:
lib1/
tests/
test_a.cpp
test_b.cpp
src/
a.cpp
b.cpp
lib2/
tests/
...
src/
...
I would then compile all of one directory's tests into an executable.
-----Original Message-----
From: boost-bounces_at_[hidden] on behalf of Ari Johannesson
Sent: Sat 4/7/2007 9:41 AM
To: boost_at_[hidden]
Subject: [boost] Boost.Test: File/build structure for Boost.Test unit
Now, my question is this: do I have one monolithic unittests.cpp file
that for all the unit tests or should I set up multiple files which is
preferable, e.g. one cpp file per class being tested.