Skip to main content

Community TFS Build Extensions: NUnit activity

For a customer I was replacing the MSTest activity inside the Build Process template by the NUnit activity from the Community TFS Build Extensions(http://tfsbuildextensions.codeplex.com/).

After configuring the activity I saw inside the build log that the NUnit tests were running fine and that the results were published to Team Foundation Server.

image

According to the documentation I should also see the results inside my build report:

image

But when I opened my report no test information was available.

What went wrong?

When the the Build report is loaded, it tries to find the related test results from the TFS database. One of the filter criteria to find the correct tests are the build platform(e.g. Any CPU,x86,…) and flavor(e.g. Debug, Release,…).  This means that if you passed the wrong information to the NUnit activity, TFS will not be able to find the test results in the TFS database.

And this was exactly what happened to me. I hardcoded the flavor inside the activity to “Release” while my build configuration was using “Debug”. After updating the flavor to the correct value, TFS was able to load the test results as expected.

image

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

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

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