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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more