Test-driven development (TDD) is an automated testing method and software

development technique that works by repeating a short development cycle, first

the developer writes a failing automated test case that defines a desired
improvement or new function, then writes a code to pass that test and then
refactors the code to improve its internal structure.
the TDD relies on the concept that "get something working now and perfect
it later. " After each test, refactoring is done and then the same or an
improved test is performed again. The process is repeated as many times as
necessary until each unit is functioning according to the desired requirements.
yet exceptional cases and error handling are not considered initially.
Test-driven development is part of a larger software design model known as
Extreme Programming (XP).
While (XP) considered as a new methodology, many of its practices have been
around for the last few decades; it takes "best practices" to extreme levels. For
example, the "practice of test-first development, planning and writing tests
before each single increment" was used as early as NASA's Project Mercury,
in the early 1960s (Larman 2003).
Because TDD tests conducted from the beginning of the design cycle , that way
we can ensure that errors are prevented by the process of unit testing
. and further approached in an incremental fashion
the concept of TDD can lead to more modularized and flexible code that is
because of the thinking of each unit of the code written and
independently tested then integrated with other units and by so we can
reduce defect density, improve software quality, and in some cases
make team productivity higher. But we cannot test everything with
. TDD, like UI, external files, and database
TDD has tools for example cppUnit, DUnit (Delphi), JUnit, XTUnit, and
.VBUnit