Pathologically Eclectic Rubbish Lister | |
PerlMonks |
Re^4: Test::Class and test organizationby dragonchild (Archbishop) |
on Mar 22, 2006 at 03:51 UTC ( [id://538395]=note: print w/replies, xml ) | Need Help?? |
Here's a basic list of the discrete tests:
It's almost a N-dimensional matrix of possibilities, and I want to be able to cover as many as possible. Now, 99.9% of these tests will not be run when the user installs. I plan on picking some representative examples that provide 95%+ code coverage in under 30 seconds on a standard machine and using those for installation tests. That suite will also be the tests that I run on a standard basis before committing changes. However, I need a suite of tests that I can run overnight (if necessary) that will completely and utterly crush this code and show me that every single edge case I can think of has been covered. Then, when a bug is found, I can demonstrate the the bug has been covered in every one of these scenarios. I need to do this so I can have the level of confidence in DBM::Deep that I have in MySQL or Oracle. A perfect example is the autobless feature. I found a few bugs in autobless in a few situations, so I fixed them. Recently, however, I found a bug with autobless when it came to exporting. Had I been using this comprehensive test suite, I would have found that bug already (and others like it, I suspect). My criteria for good software:
In Section
Seekers of Perl Wisdom
|
|