The last year I have written three blog posts for the Microsoft MSDN ALM blog on unit testing. The posts focused on the new test explorer with its abilities to run tests in multiple frameworks, and utilizing traits to filter what to run, both in Visual Studio and on TFS Build. I covered the adapters for NUnit, XUnit and Chutzpah.
The adapters can be installed either into Visual Studio using a Visual Studio Extension, or added to your solution using an adapter delivered through NuGet. At the time of writing only NUnit offers the NuGet adapter. The advantage of using a NuGet based adapter is that it follows the solution, so it will just work for any developer regardless of that developer has installed the adapter or not. It will also work directly on a TFS server, either on-premise or the TF Service.
If you use non-NuGet adapter, the content of the adapter must be added to the TFS Server custom build activities folder. This is described in Part 3 (above). Grab a readymade zip with this content.
Part 3 also describes how to get the NUnit NuGet adapters – there are two variants – and how to choose between them.
NuGet Quick Access: Search for “NUnit TestAdapter”. Note: You need only one per solution
Setting up NuGet correctly in your solution is described in this NuGet Setup Inmeta Knowledge Article
If you choose to go the extensions road, they are found at
Some other useful articles