./resources/book-test-driven-development-by-example-kent-beck.resources/unknown_filename.jpeg

Problem: dependency Symptom: duplication

  1. Write failing test BEFORE writing any code
  2. Remove duplication

get to green ASAP, quick&dirty:

tests driving code:

Results:

  • organic design
    • vs over-engineered code
  • courage
    • vs fear
    • rest between
  • self testing code

Split up

  • design
  • getting code to work

because they are conflicting activities

Model: The Three Laws of TDD

Pattern: put a bad feeling into a test Pattern: put a bad feeling into a test