I really enjoyed reading the article Ngu Soon Hui posted in his blog called Testable Code? Who Cares?
The post writes about the fact that although writing easy to maintain, testable code directly contribute to a project success most developers fail to do so. It continues explaining the reasons why proven methodologies for better code are not used in software project.
At the end of the post Ngu wrote: "Finally, a lot of developers are not writing new code; they are maintaining old code (whether it’s written by them or other people) that is not testable anyway".
I disagree – even if working with legacy code is a pain it is testable – as you can read at this post.
So once again we find that in some cases mocking not only a good practice but a must.
