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

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B
Read more

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…
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