Since we are not using MSBuild anymore, we need some tools to help us in the testing process. Below are the tools that I currently use for this:
- NUnit GUI & Console runner (included in the NUnit setup) http://www.nunit.org/index.php?p=download
- Visual NUnit – for running and debugging tests inside Visual Studio 2010 http://www.bubblecloud.org/visualnunit (if you have a productivity tool installed, such as Telerik JustCode or JetBrains Resharper, you can use that to run tests)
- PartCover – for test coverage (will detail setting up this tool in a later blog post)
- NUnitForVS – one side effect of migrating existing Visual Studio test projects to NUnit was that we are able to use the integrated Visual Studio test runner. The only issue we’ve encountered is that running NUnit tests in this way is extremely slow (maybe some configuration issue?); you can check out this blog for more information http://bloggingabout.net/blogs/vagif/archive/2010/03/06/nunitforvs-integrating-nunit-tests-into-visual-studio.aspx
The NUnit GUI & console test runner come in two flavors – AnyCPU and x86. In my project I could only run the tests using the x86 runners (I have mixed projects – some using the x86 configuration, while most are built using the Any CPU configuration).
Check out the next parts of this series here: