Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

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]
and one hand claps...

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (5)
As of 2018-03-18 08:39 GMT
Find Nodes?
    Voting Booth?
    When I think of a mole I think of:

    Results (229 votes). Check out past polls.