I think you're getting the term wrong.

TDD doesn't just mean "do a lot of tests" - it's a very specific discipline that means writing the test first, and then writing the code to make the tests work.

I am obsessive about testing - I'm the guy who writes tests for the error paths as well as the "happy path"! - but I never use TDD, and I have never worked in a TDD shop.