It is tempting to start the TDD process by writing unit tests for classes in the application. This is better than having no tests at all and can catch those basic programming errors that we all know but find so hard to avoid: fencepost errors, incorrect boolean expressions, and the like. But a project with only unit tests is missing out on critical benefits of the TDD process. We’ve seen projects with high-quality, well unit-tested code that turned out not to be called from anywhere, or that could not be integrated with the rest of the system and had to be rewritten.
- Chapter 1. What Is the Point of Test-Driven Development?
- from Growing Object-Oriented Software, Guided by Tests
- Publisher: Addison-Wesley Professional
- Released: October 2009
So true. And those dreaded test-code generators in modern IDEs simply support this nonsense.