Test Driven Development

Throughout the long term I have come to describe Test Driven Development in terms of three simple rules. They are: You are not permitted to compose any creation code unless it is to make a faltering unit test pass. You are not permitted to compose anything else of a unit test than is sufficient to fall flat, and assemblage failures will be failures.

TDD is Time-Consuming and Costly, in both Short Term and Long Term. In the previous section we've as of now discussed why TDD is tedious in short term: you need to spend significant time on refactoring and changing your code. In any case, in the long haul, it will cost additional time as well. Keep in mind, test cases are code, as well.

TDD itself is a serious simple process.

Kent Beck's description of a single TDD cycle is:

1. Add a little test.

2. Run all tests and fall flat.

3. Roll out a little improvement.

4. Run the tests and succeed.

5. Refactor to eliminate duplication.

6. Go to (1)