TDD is not a testing process. It is a design process. The tests are a secondary and beneficial artifact of the well designed software that comes from writing a test first.

> TDD is not a testing process. It is a design process.

The article actually discusses whether this is accurate or not. TDD started out as a testing process but got adopted for its design consequences which is why there is a lot of confusion.

Naming it test driven design would have gone a long way to help things and also resulted in less cargo culting. "Have to TDD all day or you don't do TDD"