Test-Driven Development

1. Don’t write a line of new code unless you first have a failing automated test

2. Eliminate duplication

Two rules of TDD

by Kent Beck

1. You are not allowed to write any production code unless it is to make a failing unit test pass.

2. You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures.

3. You are not allowed to write any more production code than is sufficient to pass the one failing unit test.

Three rules of TDD

by Uncle Bob Martin

1. Write a test for the next bit of functionality you want to add

2. Write the functional code until the test passes

3. Refactor both new and old code to make it well structured

Three rules of TDD

by Martin Fowler

About TDD

by James Shore

Some advice

Documenting

• Test naming

  • Include the method under testing

  • Add context, preconditions

  • Write what will happen, the expected behaviour

• Test cases against behaviour