
Hi,
I'd like to ask yet another questions related to Unit Test Framework
usage. Especially, I'm interested in best practice of Unit Tests
organization in the project.
I have a project that consists of more than 100 classes.
Some of those classes are general purpose (e.g. Point) but some are
organized in components (e.g. spatial index component consisting of 5
classes).
Now, I'd like to add Unit Tests (yes, I know I should have them prepared
before I created those classes ;-)).
I've read almost all docs about Boost.Test, downloaded from CVS.
I know how to create Test Case and how to combine those cases into Test
Suite. I also read introductory docs from "Tutorials and usage
recommendations" part as well as I walked through unit_test_examples but
I'm still a bit confused about the bigger picture.
As far as I understand, every Test Case or Test Suite of cases is to be
compiled to separate executable. Is this correct?
So, unit_test_example_01.cpp and unit_test_example_02.cpp and so on
create separate programs that can be executed e.g. from Visual Studio
Post-Build Event as explained in docs.
More precisely, every .cpp file that:
- include #include