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

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

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more