Keep It Simple, Stupid | |
PerlMonks |
Re^2: A danger of test driven development.by Roy Johnson (Monsignor) |
on Oct 03, 2005 at 17:56 UTC ( [id://497001]=note: print w/replies, xml ) | Need Help?? |
When "100% tests passed" or "100% code coverage acheieved" goals take a higher priority than "the code functions within specification", the real goal has been lost and the problem has arisen.
The tests are supposed to be a translation-into-code of the specification. TDD is therefore supposed to be S(pec)DD. Obviously, that doesn't always happen. What TDD does is shift the quality assurance constraint. Instead of looking at the program, you look at the tests. Bad things happen if you think that quality assurance is no longer an issue. It's every bit as important as it is in any other paradigm; it's just supposed to be easier to verify. Caution: Contents may have been coded under pressure.
In Section
Meditations
|
|