Like everyone else, we find it easy to get carried away with the simple three-step TDD cycle: fail, pass, refactor.
We’re making good progress and we know what the failures mean because we’ve just written the test.
But nowadays, we try to follow the four-step TDD cycle (fail, report, pass, refactor) because that’s how we know we’ve understood the feature—and whoever has to change it in a month’s time will also understand it.
Growing Object-Oriented Software Guided by Tests

Like everyone else, we find it easy to get carried away with the simple three-step TDD cycle: fail, pass, refactor.

We’re making good progress and we know what the failures mean because we’ve just written the test.

But nowadays, we try to follow the four-step TDD cycle (fail, report, pass, refactor) because that’s how we know we’ve understood the feature—and whoever has to change it in a month’s time will also understand it.

Growing Object-Oriented Software Guided by Tests

  1. alexandreaquiles posted this