.NET 11 Released: What QA Teams Need to Check in the New dotnet test
.NET 11 adds run-level test policies, clearer CI output, mobile test support, traversal projects, and new Microsoft.Testing.Platform options. QA teams should test these changes before upgrading.
.NET 11 expands dotnet test for CI policy and test orchestration
Microsoft released .NET 11 on November 10, 2026. For QA teams, the release's most important testing changes are in dotnet test for projects that use Microsoft.Testing.Platform, or MTP, not in the new C# language work or runtime optimizations.
The SDK now provides run-level controls for timeouts and maximum failure counts, clearer reporting for tests in progress, per-module result directories, and more flexible runner selection. It also supports mobile projects through the CLI and improves artifact handling for multi-project runs. That can remove some custom CI scripting, but runner-specific behavior still needs testing before teams update a shared build image.
Changes to test execution
- Run-level timeout: Teams can stop an entire test run after a defined period instead of relying solely on individual test or job timeouts.
- Failure limits: A run can stop after a configured number of failed tests. For a large regression suite, this prevents a widespread environment failure from producing pages of additional noise.
- Per-module results: Results can go into separate directories for each test module, which simplifies archiving and inspection for parallel or multi-assembly runs.
- Live progress: Console output shows which tests are running and includes counts for each assembly.
- Runner selection: The
DOTNET_TEST_RUNNERenvironment variable can choose VSTest or Microsoft.Testing.Platform for one session without changingglobal.json.
The runner switch is particularly useful during migration. Teams can compare VSTest with MTP in one pipeline, and developers can change runners locally, without changing the repository-wide default. The available options and their behavior still depend on the selected runner, so a command that works with VSTest may fail or behave differently with MTP.
Mobile testing moves into the standard CLI workflow
.NET 11 adds dotnet test support for Android, iOS, macOS, and Mac Catalyst test projects. New templates and device-selection options bring mobile test execution closer to the command-line and CI conventions already used for server and desktop projects.
Teams still need to verify device provisioning, signing, platform SDKs, simulators, and hosted-device connectivity. The change provides a more consistent starting point for building test projects, choosing a device, collecting results, and adding execution to a pipeline.
Traversal projects and templates cut repository setup
Repositories that aggregate many projects can now use Microsoft.Build.Traversal projects with dotnet test. The SDK expands nested traversal projects, handles duplicate references, and applies configuration and platform metadata before running tests.
The built-in xUnit template now supports xUnit v3 and can default to Microsoft.Testing.Platform. NUnit templates can opt into MTP through the test-runner option. That gives teams creating new test projects less manual setup when they want to try the newer platform.
Upgrade checks for QA and DevOps teams
- Confirm the runner. Record whether each pipeline uses VSTest or MTP. Results are not comparable without that context.
- Review timeout ownership. Decide whether the run-level timeout belongs in
dotnet test, the CI job, or both. Duplicated limits can make failures harder to diagnose. - Validate result paths. After enabling per-module result directories, check publishing, report conversion, cleanup, and retention.
- Test failure limits deliberately. Confirm that early termination still creates the artifacts and exit codes required by your quality gates.
- Rebuild the test image. Update the SDKs, workloads, mobile platform tools, and container images together. Do not upgrade only the application's target framework.
Microsoft describes .NET 11 as a Standard Term Support release with two years of support. .NET 10 remains the Long Term Support option, so support policy matters as much as the new features. .NET 8 and .NET 9 also reached end of support on November 10, 2026, making the decision more urgent for teams still running either version.
Teams with a mixed stack should roll out the change in stages. Keep the current runner as the baseline, add a .NET 11 lane, compare duration and failure diagnostics, and then migrate projects one at a time. The new controls are useful only when the pipeline treats runner choice and result layout as explicit parts of the test environment.
Looking for tools to match this read?
Jump into our independent side-by-side comparisons.
More in Tool Updates
GitHub Actions Secret Scanning Now Checks Workflow Logs: What QA Teams Need to Know
GitHub's public preview scans completed Actions workflow logs for leaked credentials. QA teams need to understand what it covers, how to enable it, and where it falls short before relying on it instead of disciplined test-pipeline hygiene.
SonarQube CLI 1.12.0 Adds Architecture Findings, Secret Redaction, and Simpler Project Administration
SonarQube CLI 1.12.0 adds architecture findings for SonarQube Cloud, redacts secrets in selected AI-agent workflows, and simplifies repository imports, project linking, and authentication management.
Karate 2.1.4 Tightens Mock Defaults, Adds Request Limits, and Improves JavaScript Compatibility
Karate 2.1.4 was released October 22, with Maven Central artifacts published October 23. The update changes mock-server defaults, adds configurable request limits, and fixes several JavaScript compatibility issues.