MBUnit vs NUnit.... The big difference for me was the ability to have data driven test cases. I have an xml file that drives the test . There is an attribute in MBUnit that will serialize an xml node (or collection through iteration) into a c# object. The object is a param to the test case. I would say most (if not all) nunit tests are parameterless. This allows me to cover all the corner cases with a single piece of code, but run different data through it. NCover works with MBUnit as does NUnit. If you have not looked at testdriven.net, you should. It allows you to run quite a few different types of tests interactively from visual studio.net.

:cool:We are using svn + tortoise instead of Source safe. Very easy to implement and less headache than cvs. After looking at all the installers, we are using NSIS (Nullsoft install system / winamp). We don't have need to generate delta's or upgrades since we host the app and only one version at a time. We are just trying to lighten the load for the IT guys. The scripting language is a bit strange, but light weight. We are using CCNET + MBUnit for continous integration testing. This was difficult to get going since we didn't easily fit into the scenarious described in the texts. Seems vastly superior to ant/nant/anthill. At the end of the day, very nice tool and with a bit more knowledge it would gone a bit faster (Thanks to jflowers / cifactory). We are using selenium + ruby for the web ui unit testing and looking at fit runners / adapters for the smart client. We are just headed down that road and don't know much yet. David Strickland / VP Software Development / Swingvote