Test‑Driven Development (TDD): Concepts, Practices, Tools, and Myths

1. What is TDD?

TDD combines test‑first development with incremental coding: a failing test is written first, then just enough production code is added to pass the test, followed by refactoring; the process repeats, emphasizing design before implementation.

2. TDD and Traditional Testing

Unlike traditional testing that validates after code is written, TDD drives development by ensuring each new feature is verified immediately, leading to higher confidence, better design, and the possibility of achieving near‑100% code coverage.

3. TDD and Documentation

Well‑written unit and acceptance tests serve as executable specifications, effectively becoming part of the system’s technical documentation and clarifying requirements for both developers and stakeholders.

4. Test‑Driven Database Development

Applying TDD to database schema changes faces tool‑support challenges, but the same principles can be used; emerging tools like DBUnit are beginning to enable database‑centric test‑driven workflows.

5. Extending TDD with Agile Model‑Driven Development (AMDD)

AMDD complements TDD by focusing on higher‑level modeling and stakeholder communication, shortening the modeling feedback loop while TDD shortens the coding feedback loop; together they provide both detailed specifications and broader design insight.

6. Why TDD?

TDD encourages small, frequent steps, fast feedback, and clean code; it improves design quality, reduces defect‑fixing effort, and scales to large projects when supported by fast test suites and appropriate tooling.

7. Myths and Misunderstandings

Common myths—such as the impossibility of 100% regression suites, difficulty testing UIs, or the notion that TDD replaces all other testing—are clarified, emphasizing that TDD is a valuable part of a broader testing strategy.

8. Who Is Doing It?

Adoption rates vary, but surveys show a growing number of teams employ both developer‑level TDD (≈53%) and acceptance‑level TDD (≈44%), indicating increasing acceptance in agile environments.

9. Summary

TDD is a disciplined development technique that, when combined with AMDD, enhances both code quality and stakeholder communication; it does not replace traditional testing but augments it, providing executable specifications and fostering continuous improvement.

10. Tools

cpputest

csUnit (.Net)

CUnit

DUnit (Delphi)

DBFit

DBUnit

DocTest (Python)

Googletest

JUnit

MoQ

NUnit

PHPUnit

TestNG

xUnit.net