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.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.