Top down development existed far before test driven development. This is just top down development instead of bottom up development.
People are angered at the number of tests relative to the size of the code base, especially if you go with something like strict 100% coverage of whitebox style tests, etc, where you're virtually guaranteed to have as many tests as function branches and then some.
Top down is an approach that has value outside the permanent test suite. You can make a more temporary suite that you use to then fill in the top down design as well, and then do not maintain.
(I am not sayings tests are bad. I'm just saying functional code is over-prioritized by some employers/customers, a well tested system is usually a good thing).