Home/ Questions/Q 667653
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T23:57:08+00:00

I hope this question is not ‘controversial’ – I’m just basically asking – has

  • 0

I hope this question is not ‘controversial’ – I’m just basically asking – has anyone here purchased TypeMock and been happy (or unhappy) with the results?

We are a small dev shop of only 12 developers including the 2 dev managers. We’ve been using NMock so far but there are limitations. I have done research and started playing with TypeMock and I love it. It’s super clean syntax and lets you basically mock everything, which is great for legacy code.

The problem is – how do I justify to my boss spending 800-1200$ per license for an API which has 4-5 competitors that are completly free? 800-1200$ is how much Infragistrics or Telerik cost per license – and there sure as hell isn’t 4-5 open source comparable UI frameworks… Which is why I find it a bit overpriced, albeit an awesome library…

Any opinions / experiences are greatly appreciated.

EDIT: after finding MOQ I thought I fell in love – until I found out that it’s not fully supported in VB.NET because VB lacks lambda sub routines =(. Is anyone using MOQ for VB.NET? The problem is we are a mixed shop – we use C# for our CRM development and VB for everything else. Any guidence is greatly appreciated again

Edit: hmm.. I can’t find Isolate.WhenCalled() equivalen in Moq… Any help here? I want to stub/mock out a ReadOnly property of a CONCRETE object (not of a mocked object)… I could easily do this with Isolate.WhenCalled with TM. How with Moq???

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The project I’m on used TypeMock for many months. We actually just finished completely phasing it out in favor of Moq (completely free Apache 2.0 licensed mocking framework). You should definitely check out Moq if you haven’t seen it. In addition to having the most intuitive syntax of any mocking tool I’ve seen, you get the benefits of compile time type checking. Very nice.

    TypeMock has one significant benefit over Moq as I see it. Namely, it can mock anything. This includes sealed classes, non virtual methods, concrete types and pretty much anything else you can throw at it. If you’re doing ASP.Net, and depending on how your code is structured, it can actually make mocking ASP.Net code behind classes a possibility. Quite neat.

    However – We found that if you structure your code well, the benefits of TypeMock do not outweigh the price. Further, if you can’t mock something with Moq, it probably means there’s a smell there. TypeMock lets you be lazy, and I think that the code can suffer as a consequence. Moq and other mocking frameworks like it (RhinoMocks comes to mind) do make you think about your code as you’re writing it, especially in terms of testability, but I would argue that’s a good thing 🙂 Further, our team ran in to several headaches trying to deploy TypeMock to our continuous integration server.

    Long story short, TypeMock is a very powerful tool. As you mention, for unit testing old legacy code there aren’t many better products. However, 1000 bucks gets you one TypeMock license, OR, a couple of resharper licenses, almost ten TD.Net licenses, a new continuous integration server or many other things. My own experience suggests that it’s not worth it, but your mileage may vary!

    • 0