I am halfway through reading Growing object-oriented software, guided by tests, a book that teaches Test-Driven Development. The book’s authors introduce a very productive practice, which consists in a double cycle of TDD: a longer cycle, where you write acceptance (aka end-to-end) tests, deriving them from the user stories or formal requirements, and make them pass; and a shorter cycle contained in the first, which happens in the phase when an acceptance test is red: you write unit tests and make them pass until the related acceptance test does not fail anymore.
Read the full article
