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.
In reply to Re: Testing 1...2...3...
by dpuu
in thread Testing 1...2...3...
by raybies
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |