Unit tests, acceptance tests, and integration tests are different things. Unit tests test that the implementation behaves as intended, and generally grope aroun

Unit tests, acceptance tests, and integration tests are different things. Unit tests test that the implementation behaves as intended, and generally grope around private internals. These change when implementation changes. Acceptance tests test that the public API is implemented correctly. These change when the API/interface change. Integration tests test that the end system implements requirements correctly, and change when requirements change. Most TDD hate comes from not separating these correctly, or not having suitable tools for each type, or from (gasp!) not actually having a clear understanding of requirements, interface, or implementation.