TestDriven.NET by Jamie Cansdale

There is a new feature in TestDriven.Net 2.24 (and 3.0 Alpha) that should greatly simplify the deployment and versioning of test runner plug-ins. In previous versions it was important that a compatible test runner plug-in was installed for each test framework you use.

For the best part of a week, I’ve been battling with the Visual Studio 2010 Beta 2 extensibility model. I’m happy to report that - finally - I’ve managed to make it bend to my will. ;-)

Fabio Maulo is doing a poll to find out which test runners people are using:

You have probably noticed with previous versions of TestDriven.Net, stack traces could turn into an unruly mess of file path information.

It turns out that the JIT compiler for x64 is considerably slower than for x86 (and uses more memory). You can easily improve the startup time for your EXE projects by changing them to compile for x86. In fact this is what Microsoft is doing in Visual Studio 2010 (the default for EXEs will be x86). It’s only worth compiling EXEs for AnyCPU if your application might use a lot of memory. See Rick Byers’ post on the subject: AnyCPU Exes are usually more trouble than they're worth.

I'm happy to report that TestDriven.NET 2.22 RTM has cleared the launch pad!

I’ve just uploaded a new version of TestDriven.Net (2.22 RTM) which is compatible with Visual Studio 2010 Beta 1.

A couple of days ago, Charlie Poole announced that the first NUnit 2.5 release candidate is now uploaded. I’ve hurried to get a new version of TestDriven.Net with support for this version ready. I’m happy to announce that TestDriven.Net 2.21 Beta (which includes NUnit 2.5 RC) is now available for download.