Typemock vs Moq [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 8 years ago.

I have heard/read a little about both of these frameworks and have decided I want to use of of the two. Which is better? Why?

Thanks in advance! Oshiwoshydopaliscious

Answer 1

Well, TypeMock Isolator is a paid product and Moq is FOSS, so that may be your decision point alone. Beyond that, I believe TypeMock provides the ability to mock statics and legacy code that is unmockable through standard polymorphism.

For blow by blow feature comparisons, there are plenty out there:

http://msmvps.com/blogs/bmains/archive/2009/11/03/moq-and-typemock-in-comparison.aspx

But, I'd say your decision amounts to what you're willing to spend. You get more "Mockability" if you pay more. So, if you're trying to retrofit tests on legacy code with lots of static, you might want TypeMock. If you're starting a green field project and have the luxury of writing testable code from the get-go, Moq is great.