chore(deps): update microsoft.testing

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Microsoft.Testing.Extensions.CodeCoverage	nuget	minor	18.8.0 → 18.9.0
Microsoft.Testing.Extensions.CrashDump	nuget	minor	2.2.3 → 2.3.1
Microsoft.Testing.Extensions.HangDump	nuget	minor	2.2.3 → 2.3.1
Microsoft.Testing.Extensions.Telemetry	nuget	minor	2.2.3 → 2.3.1
Microsoft.Testing.Extensions.TrxReport	nuget	minor	2.2.3 → 2.3.1
Microsoft.Testing.Extensions.TrxReport.Abstractions	nuget	minor	2.2.3 → 2.3.1
Microsoft.Testing.Platform	nuget	minor	2.2.3 → 2.3.1
Microsoft.Testing.Platform.MSBuild	nuget	minor	2.2.3 → 2.3.1

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[claude]

Code Review

Reviewed the diff (2 files, +8/-8). This is an automated Renovate dependency bump for the Microsoft.Testing.Platform ecosystem packages (Microsoft.Testing.Platform, .MSBuild, .Extensions.CrashDump/HangDump/Telemetry/TrxReport(.Abstractions)), all going from 2.2.3 → 2.3.0 (minor version).

Findings: None. No design, architectural, or maintainability concerns — this is a mechanical version bump with no behavioral code changes.

Verification:

• All package versions are updated consistently in Directory.Packages.props (central package management), so there's no risk of version drift across the solution.
• The one direct PackageReference in examples/CloudShop/CloudShop.Tests/CloudShop.Tests.csproj was updated in lockstep with the central version — good, this avoids a stale pinned version diverging from the CPM baseline.
• No source files, public APIs, or source-generator output are touched, so snapshot tests and dual-mode (source-gen/reflection) concerns don't apply here.

Suggestion: Since this is a minor bump of the test platform/runner itself (not just an extension), it's worth confirming CI (in progress at review time) passes fully before automerge, particularly the modularpipeline matrix jobs, since platform version bumps have occasionally introduced subtle CLI/output-format changes in this repo's history. Nothing to act on now beyond letting CI complete.

Approving from a code-quality standpoint — no changes requested.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[claude]

Code Review

This is an automated Renovate dependency bump (Microsoft.Testing.Platform and related Microsoft.Testing.Extensions.* packages: 2.2.3 → 2.3.0, Microsoft.Testing.Extensions.CodeCoverage: 18.8.0 → 18.9.0). The diff itself (Directory.Packages.props, CloudShop.Tests.csproj) is mechanical and correctly applied consistently across both the central package version and the one project with a pinned version override — no architectural concerns there.

Blocking issue: this bump breaks the build

CI is currently failing (.NET / modularpipeline on macOS, de-DE, and integration-tests) with 8 compile errors across all three target frameworks (net8.0/net9.0/net10.0):

error MTP0001: 'CancelledTestNodeStateProperty' is obsolete: Test frameworks should throw
OperationCanceledException using the cancellation token passed by Microsoft.Testing.Platform
instead of using this state. (https://aka.ms/testingplatform/diagnostics#MTP0001)

Microsoft.Testing.Platform 2.3.0 introduces an analyzer that flags CancelledTestNodeStateProperty as obsolete-as-error. This property is still used in several places in TUnit.Engine:

• Xml/JUnitXmlWriter.cs (lines 234, 400)
• TUnitMessageBus.cs (line 116)
• Reporters/GitHubReporter.cs (lines 153, 509, 540, 570)
• Reporters/Html/HtmlReporter.cs (line 622)
• TUnit.Engine.Tests/GitHubReporterTests.cs

This isn't flaky CI — it reproduces consistently across every OS/TFM combination in the pipeline, so this PR cannot merge as-is.

Suggested approach: rather than suppressing MTP0001 (which just defers the problem and keeps emitting cancellation state through a deprecated path), migrate TUnit.Engine's cancellation reporting to throw/propagate OperationCanceledException via the cancellation token Microsoft.Testing.Platform already passes through the engine, per the diagnostic's own guidance. That keeps TUnit.Engine aligned with the platform's intended cancellation model rather than accumulating tech debt behind a pragma. Given the scope (5 files touching XML/HTML/GitHub reporters and the message bus), this warrants a small follow-up PR from a maintainer/bot-adjacent contributor rather than folding it into this Renovate PR — Renovate PRs should stay mechanical.

Until that migration lands (or the obsolete member is suppressed as a stopgap with a tracking issue), this PR should stay blocked/rebased rather than merged, despite Renovate's automerge being enabled.