Personally I think it makes a lot of sense to split up your tests into seperate files, preferably based on the type of testing that will occur. When your tests start being more code than what is being tested having it all in one file doesnt make a lot of sense. I mean at the very least if your code is 100 lines, and your tests 1000 (a not unreasonably ratio IMO) then if you embed your tests in the same file thats 900 lines of code that will be read and parsed and compiled for no reason every time you use the module.
And frankly if you are using the test framework to get a pretty number telling you "XX.X% passed" then you aren't using the test framework properly. The issue is to find out what failed not what passed. Having the tests broken down into test files grouped in some sensible way, a failure from a given file can itself be enough information to start investigating. Having the actual test name is even better.
Anyway, i dont expect youll change your views based on my comments, but hopefully other readers will learn something from this.
In reply to Re^5: Self Testing Modules
by demerphq
in thread Self Testing Modules
by Sheol
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |