What we're about
Upcoming events (4)
How to focus on continuous learning even if there seem to be so many things that need to be learned.
Test-driven development (TDD) is a software development process (http://en.wikipedia.org/wiki/Software_development_process) that relies on the repetition of a very short development cycle: first the developer writes an (initially failing) automated test case (http://en.wikipedia.org/wiki/Test_case) that defines a desired improvement or new function, then produces the minimum amount of code to pass that test, and finally refactors (http://en.wikipedia.org/wiki/Code_refactoring) the new code to acceptable standards. Kent Beck (http://en.wikipedia.org/wiki/Kent_Beck), who is credited with having developed or 'rediscovered' the technique, stated in 2003 that TDD encourages simple designs and inspires confidence.
Test-driven development is related to the test-first programming concepts of extreme programming (http://en.wikipedia.org/wiki/Extreme_programming), begun in 1999, but more recently has created more general interest in its own right.
Programmers also apply the concept to improving and debugging (http://en.wikipedia.org/wiki/Software_bug) legacy code (http://en.wikipedia.org/wiki/Legacy_code) developed with older techniques.
Description taken from http://en.wikipedia.org/wiki/Test-driven_development