ronpih's weblog

At the moment i have one more question. Why not MbUnit?

http://www.mertner.com/confluence/display/MbUnit/Home

If you have access to VSTS I'd say go for it!

James Newkirk was the original developer of nUnit and then was hired on by Microsoft to lend his expertise in unit testing to VS. As a result, the unit testing experience is an incredibly integrated experience within VSTS and is an improvement over the basic capabilities found in nUnit.

I'm not discounting nUnit, which will get the job done, but things like debugging code from within nUnit are more difficult as you have to attach the debugger to the nUnit process each time you want to debug. Not sure about the active-ness of nUnit development either, last time I used it there were crashes from time to time.

If you're using VSTS with TFS, you get some additional niceties such as the ability to set check-in policy such that your unit tests must pass before checkin.

VSTS would provide a more integrated environment for unit testing and associated activities such as bug tracking, coding standards assessment, builds and project management (and even Scrum now!) but its licensing costs are not insignificant even for a relatively small team. If you already have invested in Visual Studio licences then it's easy enough to automate unit testing with NUnit in the IDE either by targetting it as a debugger or by purchasing TestDriven.NET which makes the whole process seamless.

I think that MSDN Forums or Microsoft Newsgroup are more appropriate fort this kind of questions than a Blog...