Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

Re^2: Organising Large Test Suites

by eyepopslikeamosquito (Canon)
on Jun 07, 2004 at 04:25 UTC ( #361868=note: print w/ replies, xml ) Need Help??


in reply to Re: Organising Large Test Suites
in thread Organising Large Test Suites

Personally, I would have a way of uniquely identifying each test in your test suite.
I think it's better to assign the unique id to the bug/test-case because they tend to be more stable than the test suite (especially when you start refactoring).


Comment on Re^2: Organising Large Test Suites
Re^3: Organising Large Test Suites
by dragonchild (Archbishop) on Jun 07, 2004 at 11:29 UTC
    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

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://361868]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (5)
As of 2015-07-02 06:40 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (30 votes), past polls