Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic

Re^2: when do you stop writing test?

by smahesh (Pilgrim)
on Feb 11, 2007 at 07:46 UTC ( #599437=note: print w/replies, xml ) Need Help??

in reply to Re: when do you stop writing test?
in thread when do you stop writing test?

Just to add my 2 cents to above excellent summary.

Write the proactive tests either before writing the code or in parallel with coding. The proactive tests should test against the requirements **NOT** the implementation. The requirements doc is the bible for the proactive tests.

Write the reactive tests when a bug/issue/broken functionality is detected and add it to the test suite so that a repeat offence is automatically caught.

When to stop is an open-ended question. In practice, you stop when there are no more defects in the system. In reality, you stop when no more defects are found (or when the cost of testing outweighs the benefits/number of bugs found).


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://599437]
[stonecolddevin]: oh wow sundialsvc4 is back
[karlgoethebier]: stonecolddevin: wow?
[stonecolddevin]: yes, wow.

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (7)
As of 2017-06-22 19:34 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (528 votes). Check out past polls.