Test-driven development
Coding technique of repetitively writing test code then production code / From Wikipedia, the free encyclopedia
Dear Wikiwand AI, let's keep it short by simply answering these key questions:
Can you list the top facts and stats about Test driven development?
Summarize this article for a 10 year old
Test-driven development (TDD) is a way of writing code that involves writing an automated unit-level test case that fails, then writing just enough code to make the test pass, then refactoring both the test code and the production code, then repeating with another new test case.
Alternative approaches to writing automated tests is to write all of the production code before starting on the test code or to write all of the test code before starting on the production code. With TDD, both are written together.
TDD is related to the test-first programming concepts of extreme programming, begun in 1999,[1] but more recently has created more general interest in its own right.[2]
Programmers also apply the concept to improving and debugging legacy code developed with older techniques.[3]