False.

TDD produces Developer Tests.

Although authors said in the beginning, Unit Test because they invented the tools for Unit Testing, but for them, they have a different meaning.

Under the QA definition of Unit Test is «the failure of a UnitTest implicates only one unit» of code, but with that definition is for QA that write tests when the code already exists, and when we have actual units of code.

With TDD, there is no code before test, so we cannot test units of code. What TDD tests are units of behavior. You can read that on the Agile Alliance UnitTest definition. But you can also read that on the TDD by Example book.

Btw, the section "TDD disadvantages", is in fact "People Pitfalls", not disadvantages, that is what I wanted to read. The last paragraph seems to be about it. But, it is also a lie, when you say "some detractors", it is usually people that did not learn correctly TDD, so they are not qualified to speak about it. I know because at least the first two cases are the best case for TDD. And I also know because almost anyone mistakes TDD Unit Tests, and uses QA Unit Tests, that does not work for TDD, but they blame TDD instead of asking their selves how they can fix TDD.

Please watch: TDD, Where Did It All Go Wrong by Ian Cooper, and Extreme Programming 20 years later by Kent Beck. And please fix your definition of Unit Test for TDD before creating more frustrated people.