Darrell Norton's Blog [MVP]

I've used NUnit for the last three years, but when I recently opened/imported an existing .Net 1.1 project (built in VS 2003) into VS 2005, I was never quite able to get my NUnit based test project to run under my existing version of NUnit (2.2). The NUnit gui choked and wrote out an error message about my .dll having a 'bad format.'

So I gave up.

Instead, I ported my existing unit test classes over into the new testing framework built right into VS 2005 (you have to replace method attributes like [SetUp] with attributes like [TestInitalizer()] ... ) The code you write to run in VS 2005's testing host (VSTestHost.exe) turns out to be *remarkably similar* to the code which ran in NUnit. ;-)

So far, I'm pleased with the results, and don't think I'll be going back to NUnit. (maybe i'll change my mind next week, one never knows).

In addition, I find the builtin "Web Test" macro recorder in VS 2005 is easy to use, though I'm concerned about my ability to tweak it and really bend it to my will. I'm not yet familiar enough with it to be sure, but I'm not sure it will prove to be as flexible as the NUnitASP approach. On the other hand. VS 2005's Web Tests are certainly REALLY easy and quick to create.

So, er, is VS 2005 the beginning of the end for NUnit?