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

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

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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more