Solution for unit testing SharePoint does not fix root cause

21apps.com has written an article about how to use Typemock Isolator in order to unit test SharePoint applications. According to the article, “Typemock has become the tool of choice for unit testing SharePoint as it supports faking everything including the sealed classes found throughout the object model”. Problem is that the root cause that prevents unit testing in SharePoint is an invasive API that creates dependencies between your code and the API. Using Typemock Isolator is treating the concequences without attacking the cause of the problem. But of course, having unit test is an advantage compared to having none.