[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/microsoft/testfx

• Subscription: 5e12033c-5337-464b-b504-9ec86a355360
• Build: 20261031.5 (339275)
• Date Produced: November 1, 2026 6:06:47 AM UTC
• Commit: 2a8ebadb17a3b388b62bbb0cedd407999e3ce10a
• Branch: main

• Dependency Updates:
  • From 2.5.0-preview.26477.3 to 2.6.0-preview.26531.5
    • Microsoft.Testing.Platform
  • From 4.5.0-preview.26477.3 to 4.6.0-preview.26531.5
    • MSTest
    • MSTest.Sdk

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
2 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[nagilson]

Once #56590 is green, a similar fix should be applied here

[Evangelink]

Fixed in a1e8f074aef49b017ec5ec1b6961c30b31d55c75.

All four failures reported by build 1659237 are the same stale MTPHelpSnapshotTests.VerifyMTPHelpOutput snapshot. I confirmed the identical two-line diff in the Linux x64, Windows x64, Windows FullFramework, and macOS arm64 Helix logs. The test application successfully returns help with exit 0, but its output now includes --coverage-threshold-branch and --coverage-threshold-line.

These are intentional MTP additions from microsoft/testfx#11814. I checked their definitions and descriptions at this PR's exact testfx commit, 2a8ebadb17a3b388b62bbb0cedd407999e3ce10a. The fix adds only those two lines to the verified snapshot, matching the generated release-branch output. It does not change product code, dependency versions, analyzer settings, assertions, or test selection.

Release-branch validation: Windows x64, complete built SDK layout 11.0.100-dev, bootstrap SDK 11.0.100-rc.1.26425.128, MSTest/MSTest.Sdk 4.6.0-preview.26531.5, and Microsoft.Testing.Platform 2.6.0-preview.26531.5. The actual built test application's dependency manifest confirms the MSTest and MTP versions.

Run	Exit	Result
Full SDK build, including Native AOT layout	0	Complete release SDK layout built.
Original snapshot on 5e1a1113fb8ba37e45af714311dfc2b40c8abec8	2	Reproduced the exact CI mismatch.
Corrected snapshot and help integration classes, repeated twice	0	14/14 passed, no skips.

The passing cases cover the snapshot, single-module and multi-module help, Debug and Release test applications, unavailable extension options, duplicate-option prevention, and successful parent exit codes. The updated snapshot also matches the full generated output, not merely the presence of the two option names.

Commands used:

$env:DOTNET_ADD_GLOBAL_TOOLS_TO_PATH = '0'
$env:DOTNET_CLI_TELEMETRY_OPTOUT = '1'

# The installed preview C++ toolchain and Windows system tools must be on PATH.
cmd /d /c 'set "PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\WindowsPowerShell\v1.0;%PATH%" && call "C:\Program Files\Microsoft Visual Studio\18\Insiders\VC\Auxiliary\Build\vcvars64.bat" >nul && call build.cmd -c Debug -bl'

# Before the snapshot correction: expected reproduction, exit 2.
.\.dotnet\dotnet.exe scripts\RunTests.cs -- --project test\dotnet.Tests\dotnet.Tests.csproj --filter 'FullyQualifiedName~MTPHelpSnapshotTests'

# After the correction: exit 0, seven cases per iteration.
.\.dotnet\dotnet.exe scripts\RunTests.cs -- --project test\dotnet.Tests\dotnet.Tests.csproj --filter 'FullyQualifiedName~MTPHelpSnapshotTests|FullyQualifiedName~GivenDotnetTestBuildsAndRunsHelp' --repeat 2

This release branch predates the centralized runner, so I used an unmodified temporary copy of scripts/RunTests.cs from SDK commit 64bb526f36a4537da9993214be583894180e5fee, then removed the temporary checkout copy. The runner is not part of this fix.

Retained local evidence: the before-fix TRX/binlog under artifacts\log\test-runs\dotnet.Tests\20261105-105605-77972, and both passing TRX files plus their build binlog under artifacts\log\test-runs\dotnet.Tests\20261105-105728-71536. The full build binlog is artifacts\log\Debug\Build.binlog. Existing NuGet audit warnings were not suppressed.

This verifies the correction locally on the shipping release branch; it is not a claim that the newly triggered cross-platform CI run has finished.