Tjen Wellens

Tjen's blog

  • Home
  • Archive
  • About
  • Contact

Book: Test Driven Development: By Example - Kent Beck

i.booktddp.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:

  • Pattern: Fake it until you make it

  • Pattern: TDD Obvious Implementation

 

tests driving code:

  • Pattern: Triangulation

 

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: Make the change easy. Then make the easy change. copy

Pattern: put a bad feeling into a test

This post was referenced in:

  • Journal: Object Calisthenics + TDD + Advent of Code - day 1
  • Journal: Object Calisthenics + TDD + Advent of Code - day 1
  • Pattern: Make the change easy. Then make the easy change.
  • Pattern: put a bad feeling into a test
  • Pattern: Triangulation
  • Pattern: Obvious Implementation
  • Pattern: Fake it until you make it
  • Practice: Object Calisthenics + TDD + Advent of Code
  • Video: TDD, Where Did It All Go Wrong - Ian Cooper
  • Journal: Object Calisthenics + TDD + Advent of Code - day 2