I think I agree with this. We do TDD and the first test we write for a new module is usually a high-level test that walks entirely through the process, touching

I think I agree with this. We do TDD and the first test we write for a new module is usually a high-level test that walks entirely through the process, touching several classes or libraries. Then we write smaller tests, working our way down to fine-grained level with multiple tests for individual classes/functions. We catch errors at every level, and the end result is (usually) clean, bug-free code. My understanding is that this is frowned upon from a TDD purist standpoint. Our high-level tests that touch lots of areas of code probably wouldn't be written in most shops.