TestDriven.NET + TypeMock.NET

I have recently been working with Eli Lopian from TypeMock so ensure that TestDriven.NET and TypeMock.NET work nicely together. TypeMock is a mocking framework that allows virtually any .NET Type to be mocked (the only exception being types defined in mscorlib).

I am now using TypeMock to test certain assemblies that make up the up TestDriven.NET application. These are assemblies use the Visual Studio extensibility model. In the past I have tested this code by creating an instance of Visual Studio and doing integration tests. The problem I have is that I still need to test against Visual Studio .NET 2002 and 2003. I don't always want to have these installed on my development machine.

One possibility is to execute these integration tests whenever code is checked in and picked up by CruiseControl.NET. Unfortunately this means finding problems after the code has been checked in. I much prefer to run my tests and catch bugs before it gets this far!

I'm certainly not advocating using TypeMock in all of your unit tests. There are however some situations where using it makes a lot of sense. I think there is a sweet spot somewhere between unit tests and integration tests that TypeMock is particularly suited for.

You can can download and find more information about TypeMock here. There are community (free), professional and enterprise versions. We have worked out a offer so that if you buy TypeMock.NET and TestDriven.NET together you get 25% off. Since I am using TypeMock myself, you can expect the integration to get better and better. :)