Jon A. Cruz wrote:
At the moment there are reasons to keep things separate...
... however with CxxTest, it's simple to have things individually *and* combined. We might have some of that already set up.
OK, but what are those reasons to keep CxxTests separate? As I see it, this has a number of disadvantages: 1. Lots of error-prone makefile boilerplate needed 2. Test logs are scattered all over the build directory 3. Building and linking the tests takes more time 4. Each test has to specify which libraries it needs 5. We need the test-stubs.cpp file with a stub preferences implementation
The only advantages I see are: 1. If some test crashes, others can run (but then it's an obvious error either in the testand should be corrected right away) 2. The number of failed tests shown after "make check" is slightly more meaningful 3. Higher chance of conflicts between test headers (I encountered only one and corrected it already)
My single-test implementation uses a variable named CXXTEST_TESTSUITES, to which all test headers are appended in Makefile_inserts. The only test-related thing left in Makefile_inserts is the list of test headers. I think it's more convenient and simpler than the exisitng system.
Regards, Krzysztof Kosiński