Book: Test Driven Development: By Example - Kent Beck

September 30th, 2015

 

no description for image available

 

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

  • self testing code

 

Split up

  • design

  • getting code to work

because they are conflicting activities

 

Pattern: Make the change easy. Then make the easy change. copy

Pattern: put a bad feeling into a test