.NET 10 + MTP Broke Azure DevOps Tests? | Fix dotnet test and Coverage

Published 18/11/2025

Description

After moving to .NET 10 and enabling Microsoft.Testing.Platform in global.json, my Azure DevOps pipeline started failing even though dotnet test worked correctly on the build machine. Microsoft says that starting with .NET 10, dotnet test has native Microsoft.Testing.Platform support and expects all test projects to use Microsoft.Testing.Platform when it is opted in through global.json. In this video, I walk through the full pipeline failure, show why older Azure DevOps test task assumptions break once MTP is enabled, and then replace the brittle setup with a direct dotnet test call that uses the newer MTP-style arguments for coverage and results. Microsoft’s Azure DevOps task reference now documents MTP-aware coverage options such as --coverage, and Microsoft later added first-class DotNetCoreCLI support for Microsoft.Testing.Platform in task version 2.263.0. 0:00 - Introduction 0:19 - Description 1:38 - Failed Build 2:21 - Build Machine Initial Test 2:53 - Pipeline Task 3:23 - Build Machine Debugging 5:33 - What is lost 6:28 - Pipeline PowerShell Task 8:20 - Conclusion This walkthrough is especially useful if you are on Azure DevOps Server, an older task version, or a pipeline that still assumes VSTest-style dotnet test arguments. Microsoft’s current documentation makes the platform shift explicit, but older pipelines can still fail if they pass arguments that no longer match the selected test runner. #DotNet10 #AzureDevOps #MicrosoftTestingPlatform Follow me on X: https://l.samayas.eu/jo3eaYEf3E?P=YT&V=54 Buy me a Coffee : https://l.samayas.eu/jX6xL7EWhd?P=YT&V=54 Studio Equipment Camera Sony Alpha ZV-E10 II: https://l.samayas.eu/k7y90TREl0?P=YT&V=54 Secondary Camera Obsbot Tail Air: https://l.samayas.eu/iFQu9WfmCw?P=YT&V=54 Elgato Prompter: https://l.samayas.eu/fHVrqqXtSc?P=YT&V=54 Microphone Rode Wireless GO II: https://l.samayas.eu/afBINjiBXN?P=YT&V=54