Daok named all the pro’s of Visual Studio 2008 test projects. Here are the pro’s of NUnit.
- NUnit has a mocking framework.
- NUnit can be run outside of the
IDE. This can be useful if you want
to run tests on a non-Microsoft build server,
like CruiseControl.NET. - NUnit has more versions coming out
than visual studio. You don’t have
to wait years for a new version.
And you don’t have to install a new version of the IDE to
get new features. - There are extensions being developed
for NUnit, like row-tests, etc. - Visual Studio tests take a long time
to start up for some reason. This is
better in Visual Studio 2008,
but it is still too slow
for my taste. Quickly running a test
to see if you didn’t break something
can take too long. NUnit with
something like Testdriven.Net to run
tests from the IDE is actually much
faster. Especially when running
single tests.
According to Kjetil Klaussen, this is caused by the Visual Studio testrunner. Running MSTest tests in TestDriven.Net makes MSTest performance comparable to NUnit.