Wrong!

TDD focuses heavily on unit tests, as it is a unit of behavior and not a unit of code. An excellent example of it is BDD. BDD is a form of TDD, and created to teach good TDD practices.

It is curious because you cite Robert C. Martin, but you contradict some of his teachings. In fact, nothing forces you to implement QA Unit Tests (unit of code) in the implementation of an Agile Unit Tests (unit of behavior). For example, in the video https://cleancoders.com/episode/clean-code-episode-37, he shows how some tests must be e2e tests, but for most of the cases it is not necessary. The kind of test chosen is a matter of implementation details. So, it is not true that it requires a QA Unit Test that isolates everything.

And, I do not how, or why, but until today's date, every time that I read an article against TDD, every time, the author fails in the same fallacy of assuming that TDD requires QA Unit Tests. These kinds of tests are deadly for TDD.