AMDG Simonson, Lucanus J wrote:
My unit test does return non-zero error code. I consider any failure to be critically important, so if I had multiple failures I imagine I would fix them one at a time until all were fixed and the unit test passes. Having multiple files would help in the circumstance where multiple developers are breaking and fixing different pieces of the code simultaneously. Since I was the sole author I didn't need to provide a testing methodology suitable for team development. Also, it is possible for different developers to make changes on a branch and have unit test passing be a requirement for checking into the trunk.
For me a more important reason to separate the tests into multiple translation units is that by doing so a compilation failure in one file will not mask other failures in other files. This makes it easier to tell how close the library is to supporting a particular compiler. In Christ, Steven Watanabe