However if you start doing arbitrary rewrites of code aimed at breaking the test suite you're no longer doing TDD :-)
This isn't really surprising since you should not be writing code with TDD that isn't being exercised by a failing test.
No one is talking about arbitrary rewrites. Refactorings can easily result in green-bar code that wasn't immediately motivated by failing tests and that contains untested branches.
This doesn't mean that I think more traditional white box testing, branch coverage, statement coverage, etc. are useless - far from it. They're excellent tools and you can find many bugs with them.
Seems we aren't really in much disagreement after all. My original point was only that too often I've seen TDD adopted "at the expense" of more traditional testing methods rather than as a complementary "design" process.
In reply to Re: Re^5: Automatic generation of tests
by Anonymous Monk
in thread Automatic generation of tests
by DrHyde
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |