3 ms·

I thought programs spent 80% of their time in 20% of the code? TDD "code coverage" always seemed like a misguided breadth-first approach that needed to be dept

I thought programs spent 80% of their time in 20% of the code? TDD "code coverage" always seemed like a misguided breadth-first approach that needed to be depth-first primarily and breadth-first as needed. But I think the latter approach then leads to integration testing as the primary approach, so TDD zealots will hate that.

cam- 12y ago
Unit testing is a leading indicator. The higher the coverage the better the quality of the product is a good broad rule. Engineers hate unit testing to 100% until they do, and then they don't go back, it becomes the norm for their development process. The confidence and assurance you get from that level of coverage is amazing. It takes the stress out of software.