Developer News

TestDriven.Net 2.19: Release NotesWhich Test Runner? The latest version of

July 2, 2009 – 9:01 am

TestDriven.Net 2.19: Release Notes

Which Test Runner?

The latest version of TestDriven.Net will display the name of the test runner used in the test results summary. If the target project doesn t reference a known test framework assembly, TestDriven.Net will use the Ad hoc test runner to quickly execute the target method.

You can see the above method has been executed using the Ad hoc test runner. If this happens when targeting real unit test, the chances are a test runner to handle the target test type or version hasn t been registered.

NUnit 2.5 Beta 2 Support

This version includes support for NUnit 2.5 Beta 2. The previous version had a bug that caused tests that threw an exception to show as skipped rather than failed.

Test With > .NET 1.1 on a 64-bit OS

If the .NET 1.1 SDK is installed and you re using Visual Studio 2005, you will have the option to Test With > .NET 1.1 . Under the covers this functionality builds your project using MSBee before executing your tests using .NET 1.1. This will now work when executed on a 64-bit OS.

I d be interested to hear if there s any demand for this feature on Visual Studio 2008.

Visual Studio 2003 Support

This version once again works on Visual Studio 2003. Only one person noticed this was broken on the previous beta. Are there many projects still being developed using Visual Studio 2003? I m using MSBee for all my legacy .NET 1.1 support.

Running xUnit tests on a 64-bit OS

Some people have been experiencing problems registering the xUnit test runner on a 64-bit OS. It turns out the problem was due to xUnit sometimes registering itself under HKLM and sometimes under HKCU depending on what was previously installed. If you re experiencing this problem, try re-registering xUnit (using xunit.installer.exe) after installing this version.

Clear Error List Before Build

Failed tests will now be removed from the error list when a new build starts. This prevents failed tests from becoming mixed up with build errors. I think this is the correct default behavior.

Download

You can find the release notes here and download here.

Expression Design Resources
Following on from my post about the Expression family, I said I?d follow up with some more details on Expression Design. Someone commented on my other post that Expression Design is ?too basic? and I suppose for many people that will be a fair criticism. For someone like me, who?s not a graphic designer, I find it strikes a good balance between functionality and complexity (and I use some other tools to achieve things Design is not so suited to such as manipulating bitmap images ? Paint.

Guantanamo: The Game, The Controversy
Moazzam Begg, former Guantanamo Bay detainee, is set to go back to the now closed suspected terrorist prison camp. But this time his stay will be purely virtual, on the Xbox 360. As strange as it might sound, a new computer game is being developed based upon life in Guantanamo Bay according to reports. 41 year old Brit Begg spent the best part of two years there, detained as a terror suspect. He was eventually released without charge. Game play will not, however, revolve around lengthy political campaigning, nor indeed water boarding or other torture activity. There is no word on whether…

See you at @media09? Tickets are still available
Lauren and I set off for London later to today. It?s @media time again and I?ve been looking forward to this for a while. As usual Patrick Griffiths has lined up a fantastic group of really inspirational speakers and, whilst smaller in the light of the current climate, I have no doubts that it will be useful. I?ve been to every @media since it started and I?ve always had a great time. If you have the time, I?d urge you to make this year the sell-out it?s been in the past!

TestDriven.Net Options Pane

In the latest version of TestDriven.Net you will find a new options pane. The options are as follows:

Hide trace/debug output when running all tests in project/solution

In the past this setting has always been hardwired to true. It means you can add trace information to a test without cluttering up the Test output pane when all tests are executed. An alternative way to ensure a message will always appear in the output is to use Console.WriteLine rather than Trace.WriteLine . This also means the verbose Gallio/MbUnit test run output will show up when executing all tests in a project.

Cache test process between test runs

By default the external test process will be cached when the Run Test(s) command is used. This process appears in the tool tray as a rocket icon which can be used to kill the process. This is fine unless one of your tests starts leaking leaking native resources (such as leaving open a file handle). The best solution is to fix the resource leak, but you now have to option to work around the issue by killing the test process at the end of each test run. This can be useful if the resource leak is in a 3rd party DLL which can t be easily be changed.

Categories

This option supports the most common use of test categories; you can choose to include or exclude a selection of categories. This is useful if you want to exclude long running tests or if your machine isn t configured to execute integration tests. This feature is currently only supported by the NUnit runner that comes with TestDriven.Net, but I believe it will be supported by a a future version of Gallio.

You can specify your NUnit test categories like this:

    [Test, Category("LongRunning")] 
    public void LongRunning() 
    { 
        Thread.Sleep(10000); 
    } 

There are lots of features in TestDriven.Net that could be exposed as options. I ll try to resist this temptation as much as possible, but I m sure a few more will creep in.