|
|
|
| Pathologically Eclectic Rubbish Lister | |
| PerlMonks |
Re^3: Organising Large Test Suitesby dragonchild (Archbishop) |
| on Jun 07, 2004 at 11:29 UTC ( #361946=note: print w/ replies, xml ) | Need Help?? |
|
If you give each test a unique identifer, you can also track which tests handle which requirements. I know this would be useful for other reasons. The ID should be something that is on the test-level without reference to which file or subsystem it deals with. Maybe, an order of creation? Then, the test suite is actually just a list of the individual test IDs that should be run? ------
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose I shouldn't have to say this, but any code, unless otherwise stated, is untested
In Section
Meditations
|
|
||||||||||||||||||||