I have been using TypeMock for over a year now and I cannot work on a project without it. I heard a lot of people saying that TypeMock is too strong, but what if this is so? Having all this power does not make me poorly program my code.
I messed up with other fake frameworks, but what I like about TypeMock is that it can mock anything without having to create interfaces everywhere, as some mocking frameworks can only mock an interface, not the actual object. This is emphasized by my current work, which develops code in SharePoint. Without TypeMock, I could not write good unit tests. I can't see Moq or RhinoMocks allowing me to mock SharePoint object model code. Correct me if I am mistaken in this question.
Another great plus with TypeMock is support from the company. Their developers are always active in company forums, so if you have a problem, they can quickly help you. This help can either come to a forum question that you may have posted, or actually contacted you by email, if your problem is more involved, then an answer to the forum can be provided.
The only point to merge with TypeMock is value; it is not a cheap product. However, the amount of time it saved me when testing (and the flexibility I get when writing my tests) made it a worthy purchase.
Jason evans
source share