Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

Re: Testing 1...2...3...

by dpuu (Chaplain)
on Dec 20, 2010 at 23:09 UTC ( #878123=note: print w/replies, xml ) Need Help??

in reply to Testing 1...2...3...

Tests are simply one way of adding redundancy to your code with the idea that reification of a concept is less likely to be incorrect if it is implemented in two different ways. There are other ways to add this redundancy, for example assertions (assuming you have a tool that does model-checking) or static type system annotations.

Whenever you add redundancy, you also add inertia -- resistance to change -- because now each change that you make must be made in (at least) two places: ideally two different ways in those two places.

use-case testing is almost always necessary because it is unlikely that any specification can fully capture the nuances of the requirements. Unit testing is somewhat more fungible.

Opinions my own; statements of fact may be in error.

Log In?

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

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (4)
As of 2016-10-23 02:45 GMT
Find Nodes?
    Voting Booth?
    How many different varieties (color, size, etc) of socks do you have in your sock drawer?

    Results (300 votes). Check out past polls.