Skip to main content

TFS 2017 Build- MSTest v2 tests are not recognized

After upgrading our unit tests to MSTest v2 we noticed that our tests were no longer discovered by the VSTest task on our build agent.

As a solution, we decided to invoke the test execution ourself.

Therefore I added 2 tasks to our Build definition:

  • One command line task to execute dotnet test

image

  • One task to collect and publish the test results

image

In the command line task I configured the following settings:

  • To execute the dotnet command we specify ‘dotnet’ as the Tool
  • We also specify the following arguments:
    • test: we want to execute the test commando
    • --no-restore: the package restore already happened in a previous build step and shouldn’t be re-executed here
    • --no-build: assembly compilation already happened in a previous build step and shouldn’t be re-executed here
    • --logger:trx: output the test results in the trx format
  • A last important setting that we change is the ‘Continue on error’ setting is set to true. If we don’t do this, a failing test will stop any further execution of the other build steps so we never get a chance to publish the test results.

clip_image002

In the publish test result task I configured the following settings:

  • Test Result Format: VSTest; Our tests are executed using MSTest and published using the VSTest format.
  • Test Results Files: **/*.trx: Search for all trx files found and publish them
  • Merge Test Results: True; Merge all test results if multiple files are found.

clip_image002[5]

After configuring these steps, we were able to succesfully run our tests and publish the results.

Remark: We are still using TFS 2017 Update 1, a newer version of the Test task exists where this problem is gone.

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