Test Driven Development

  • Originally described in Kent Beck’s book “Test-Driven Development” from 2003

Test Driven Development principle is that:

Working code is better that Beautiful code.
- Richard Donovan

Three Simple Steps

First: write a test that verifies a small piece of desired functionality as per requirements.

Second: Make the test run/pass the test no more no less. Don't be concerned about the design of code, just get it to work.

Third: Clean up the code ensuring the code stays working correctly.

  • remove any duplication
  • check for strong coupling and loose cohesion

Test Driven Development Articles

test_driven_development.txt · Last modified: 2010/01/07 08:39 by root
RSS - 200 © CrosswireDigitialMedia Ltd