TestDriven.NET by Jamie Cansdale

TestDriven.Net 2.21: Now includes NUnit 2.5 RC

Support for NUnit 2.5 RC

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.

This is a major NUnit release with lots of new features. Here is the list that was posted on the NUnit mailing list:

1. Parameterized (data-driven) tests are supported, with features similar to those found in mbUnit and xUnit.net.
2. Theories - as used in JUnit- are supported fully, including support for Assume.That.
3. New attributes allow the specifying the thread and apartment state requirements of a test.
4. Exception handling can now be moved into the test code using Assert.Throws or the Throws.Exception syntax.
5. Test methods and fixtures may now be generic and many asserts and constraint expressions now support generic syntax.
6. Many constraints now permit substitution of a user-defined comparison algorithm through the Using modifier. Lambda expressions are supported.
7. Test execution may now take place in a separate process for better isolation.
8. Tests may be loaded and executed using a selected runtime version.
9. Tests, setup methods, teardown methods and data sources may be static if desired. If there are no instance methods, then NUnit doesn't need to construct your test class.
10. Source code is displayed in the gui, where available.

Charlie has also posted a top 10 reasons try NUnit 2.5.

Improved x86 / 32-bit support on a 64-bit OS

This version also contains improved support for running tests in a 32-bit process. To configure a test project for 32-bit execution, simply select ‘x86’ as the ‘Platform target’ in the project properties. After doing this, the ‘Run Test(s)’ and ‘Test With > NUnit 2.5’ commands will execute your tests in a 32-bit process (this doesn’t work for NUnit 2.4). By default projects configured for ‘Any CPU’ will execute tests in a 64-bit process (unless you’re testing with NCover, Team Coverage or dotTrace).

Experimental Visual Studio 2010 support

TestDriven.Net was working with the Visual Studio 2010 PDC CTP version. Unfortunately I’ve had less luck with more recent pre-Beta versions (Visual Studio was crashing). You can try the experimental support by choosing ‘Custom’ setup and enabling the ‘Visual Studio 2010’ feature. There is a chance this will be working again when the Visual Studio 2010 Beta is released.

Trace/debug messages now appear in ‘Debug’ pane

When stepping through code started from TestDriven.Net, you may have noticed that trace/debug messages appeared in the ‘Test’ pane but not the ‘Debug’ pane. Trace/debug diagnostic messages will only appear in the ‘Test’ pane when targeting specific tests, but not when executing all tests in a project / solution.

Release Notes & Download

Here are links to the TestDriven.Net release notes and download.

Don’t hesitate to contact me or the NUnit team if you find any issues with this release.

TestDriven.Net 2.20: Improved NCover Integration

In the latest release of TestDriven.Net, you’ll find much improved integration with all versions of NCover:

Support for 64-bit Windows

‘Test With > Coverage’ now works on 64-bit versions of Windows. In previous versions this could be made to work by compiling your test project for x86. The new version will automatically execute your tests in a 32-bit process if a 64-bit version of NCover can’t be found. (There is similar 64-bit Windows support for dotTrace and Team Coverage)

No more ‘Reload coverage file?’ dialog

NCoverExplorer 2.1 & 3.0 will no longer prompt to reload the coverage file. The coverage report will automatically refresh when new data is available. If you’re using NCover 3.0.18 or higher, you won’t be prompted to save a ‘New Project’ when you close NCoverExplorer.

Automatic assembly filtering

If you’re using NCover 3.0, only assemblies that have a corresponding PDB file will appear in the ‘Explorer’ window. I’m hoping this is a good alternative to explicitly naming assemblies that shouldn’t appear in the coverage support.

Support for Typemock Isolator

You can now execute ‘Test With > Coverage’ with NCover 3.0 and Typemock Isolator installed. (Previous versions would fail with the error: ‘Couldn't find TypeMock profiler name for NCover 3.0’.)

Recommended Versions of NCover & Typemock

If you have a commercial license for NCover, make sure you’re using NCover 3.0.18 or later. If you’re using Typemock Isolator, I recommend you use at least version 5.3.0.

If you’d like more timely updates on new releases, you can find me on twitter here.