Re:Why Most Unit Testing is Waste [pdf]
by masmullin on Thursday March 06, 2014 @02:59PM
(#7356185)
Unless the rewards of crapping-up the code is very high, I find this result highly unlikely.
[ Parent
| on HN ]
Happens all the time with TDD. The worst case scenario is when the code is split up into tiny interfaces that don't represent anything, and the implementing classes have myriad of tiny methods, which also don't represent anything. App logic is effectively composed during run time, and impossible to analyze by looking at the code. Every single method is unit-tested, but their interactions are not (yay, mocking!).