Test Driven Development


The idea behind test driven development is to start writing a test, before you do any coding. If you want to be strict about it the following rules lead you to glory and honor.

  • just write code to pass a failing unit test

  • once the unit test passes you are not allowed to continue on the coding side


  • start coding from general apects to specifics

    • What do I need?

    • How does the interface look like?

    • What are the parameters?

  • focus on a small pieces (an iterative approach)

  • issues do not accumulate

  • ensures 100 % code coverage


  • works well on greenfield projects

  • counter intuitive