Developer News

TestDriven.Net 2.11: Parameterized NUnit TestsTestDriven.Net has always supported parameterized test

TestDriven.Net 2.11: Parameterized NUnit Tests

TestDriven.Net has always supported parameterized test methods when used with the MbUnit testing framework. When using MbUnit, it is common for a single test method to execute multiple tests with different parameter inputs. The most famous of these test types is the MbUnit RowTest.

Until now there has been little reason to add support for executing parameterized tests using NUnit (historically NUnit has only supported parameterless test methods). However Andreas Schlapsi has recently written an implementation of MbUnit’s RowTest using NUnit 2.4’s Addin extensibility mechanism.

I’ve updated TestDriven.Net 2.11 to better support NUnit add-ins and enable the targeting of RowTests and other parameterized test types. This version also includes a workaround for a log4net related issue that was causing a noticeable delay when launching the NUnit 2.4 GUI. You can find the release notes for TestDriven.Net 2.11 here.

To install the RowTest Extension for NUnit you will need to do the following:

1. Download and install TestDriven.Net 2.11.
2. Download the RowTest Extension for NUnit 2.4.5 (Binary).
3. Create a directory called ‘addins’ in ‘%ProgramFiles%\TestDriven.NET 2.0\NUnit\2.4′.
4. Copy the ‘NUnitExtension.RowTest.AddIn.dll’ file into the ‘addins’ directory (don’t put any non-assembly files there).
5. Add a reference to ‘NUnitExtension.RowTest.dll’ from your NUnit test project.

You can then start writing and executing MbUnit style RowTests inside your NUnit projects! You can find Peli’s original RowTest example here.

To view your RowTests inside the NUnit GUI you will need to use ‘Test With > NUnit 2.4′. You will find this option on the ‘Solution Explorer’ project context menu.

Thanks to Wayne Brantley for letting me know about the RowTest Extension for NUnit.

CodeSnip: Unexpected behavior with C# auto-implemented properties
In this code snippet, Joseph examines a scenario of an unexpected behavior which will happen while using C# auto-implemented properties with reflection. After providing a step-by-step description of the scenario, he provides the complete code listing of all the C# files used in the sample project along with a screenshot of the final output and the relevant Visual Studio 2008 project.
Joseph Chahine

VS 2008 crashes on startup when ‘Code Analysis Tools’ feature is not installed

Now that Visual Studio 2008 RTM is out I have started getting reports of Visual Studio crashing on startup when TestDriven.Net is installed. I was pretty dismayed as TestDriven.Net has included Orcas support since January of this year and this support has been pretty well tested. I certainly wasn’t expecting to see any fatal crashes!

It turns out that this crash only happens when the user has opted not to install the ‘Code Analysis Tools’ feature. This is quite common when someone is doing a minimal install of Visual Studio with just the language feature they need.

The issue appears to be related to the Visual Studio command bars. If you simply query for a command bar that doesn’t exist, Visual Studio will quit with an error (rather than throwing the expected ArgumentException)!

I’m happy to say there are now two possible fixes for the issue:

1. If you go into the Visual Studio 2008 Team Suite setup and enable the ‘Code Analysis Tools’ feature, you should find the crash goes away.
2. I’ve just released TestDriven.Net 2.10, which includes a workaround for this issue. Please read the release notes and download it from here. If you’re using Visual Studio 2008 I strongly encourage you to install this version.

Thanks to Aaron Jensen, Chad Myers and Dru Sellers for reporting the problem.

Can anyone please help me with connect to database
sorry for annoying, i am quite stupid in it.