Skip to main content

Team Foundation Server 2015–Enable NUnit tests for new Build system

I’m working on replacing the existing build system we use based on XAML Workflow by the new build system introduced in TFS 2015. So far, I really like the experience. Customizing became a lot easier than it was before…

However one of the things I noticed that no Test Results were collected.

 

I opened up the Test Assemblies Step in the build process(click on the step in the Build Results).

image

There I could see that the vstest.console.exe was invoked but that no tests were discovered.image

The reason is that I’m using NUnit and therefore a test adapter should be installed and loaded on the build server.

Enable NUnit Test Adapter for TFS Build

To enable the NUnit Test Adapter, you have multiple options:

Option 1- Use the NUnit Test Adapter DLL’s

  • Log in to your build server
  • Download the NUnit Test Adapter for Visual Studio from the Visual Studio gallery: https://visualstudiogallery.msdn.microsoft.com/6ab922d0-21c0-4f06-ab5f-4ecd1fe7175d
  • Extract the VSIX file(don’t install it!) and copy the DLL’s to the following folder
    • C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\Extensions
  • After installation,  go back to the TFS web portal and open the Team Project where you want to configure the build for
  • Go to the Build tab
  • Queue a new build

Option 2 – Use the NUnit Test Adapter Visual Studio Extension

  • Log in to your build server.
    • Remark: When you use this option, it’s important the account you use to log in is the same account that is used to run the tests
  • Download the NUnit Test Adapter for Visual Studio from the Visual Studio gallery: https://visualstudiogallery.msdn.microsoft.com/6ab922d0-21c0-4f06-ab5f-4ecd1fe7175d
  • Install the VSIX file
  • After installation,  go back to the TFS web portal and open the Team Project where you want to configure the build for
  • Go to the Build tab
  • Right-click on the build definition and choose Edit…
  • Select the Visual Studio Test step
  • On the right, expand the Advanced section
  • Add the ‘/UseVsixExtensions:true’ in the Other console options field

image

  • Save the edited build definition
  • Queue a new build

Option 3  - Include the NUnit Test Adapter using NuGet

  • Open the solution you want to build in Visual Studio
  • Add the NUnit Test Adapter NuGet package(https://www.nuget.org/packages/NUnitTestAdapter/) to your solution
  • Browse to the TFS web portal and open the Team Project where you want to configure the build for
  • Go to the Build tab
  • Right-click on the build definition and choose Edit…
  • Select the Visual Studio Test step
  • On the right, expand the Advanced section
  • Add the ‘$(Build.SourcesDirectory)\packages’ in the Path to Custom Test Adapters field

image

  • Save the edited build definition
  • Queue a new build

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.