in reply to
Re^2: Organising Large Test Suites
in thread Organising Large Test Suites
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?
We are the carpenters and bricklayers of the Information Age.
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