These kinds of articles criticising unit testing always seem to work out more to do with the way people go about composing their software and the design. Inter

These kinds of articles criticising unit testing always seem to work out more to do with the way people go about composing their software and the design. Interface explosion and unnecessary abstractions as presented in the first part is often the nightmare people get into early in the their software development journey. But that's a problem with design. Possibly unit testing lead you down that path, or perhaps that path was shown to you by some advocate of unit testing. In the article even the final code seems too messy for my tastes, also could be simpler and more modular. Which then makes the testing more straight forward and you'd pretty much the same thing in the end.