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
Labels:

Popular posts from this blog

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.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more