chore(deps): update .net test stack

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
Microsoft.NET.Test.Sdk	18.0.0 -> 18.0.1
NUnit.Analyzers	4.10.0 -> 4.11.2
Verify.NUnit	31.0.1 -> 31.7.2

---

Release Notes

microsoft/vstest (Microsoft.NET.Test.Sdk)

v18.0.1

What's Changed

Fixing an issue with loading covrun64.dll on systems that have .NET 10 SDK installed: https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/code-coverage-dynamic-native-instrumentation

• Disable DynamicNative instrumentation by default by @​nohwnd in #​15298
• Update MicrosoftInternalCodeCoveragePackageVersion to 18.0.6 by @​nohwnd in #​15312

Internal changes

• Update VersionPrefix to 18.0.1 by @​nohwnd in #​15301
• Update build tools to 17.8.43 by @​nohwnd in #​15305

Full Changelog: microsoft/vstest@v18.0.0...v18.0.1

nunit/nunit.analyzers (NUnit.Analyzers)

v4.11.2: NUnit Analyzers 4.11.2 - November 2, 2025

Compare Source

NUnit Analyzers 4.11.2 - November 2, 2025

This release of the NUnit Analyzers fixes a problem in the NUnit2057 analyzer for unnecessary use of lambda
expressions. The release also extends NUnit2021 so that it can determining if Is.NaN or Is.Not.NaN constraints
are used on incompatible types.

The release contains contributions from the following users (in alphabetical order):

• @​MaceWindu
• @​manfred-brands
• @​stevenaw

Issues Resolved

Features and Enhancements

• #​929 Alert when using Is.NaN or Is.Not.NaN on an incompatible type

Bugs

• #​945 [NUnit2057] Reported for Throws assert

v4.11.1

Compare Source

This release of the NUnit Analyzers fixes a regression related to the analysis of nullable enum parameters in
NUnit1001 and NUnit1031. The release also contains a new analyzer and codefix for unnecessary usage of lambda
expressions in asserts.

The release contains contributions from the following users (in alphabetical order):

• @​MaceWindu
• @​maksim-sovkov
• @​manfred-brands

Issues Resolved

Features and Enhancements

• #​927 Add new rule for unnecessary use of lambda expressions

Bugs

• #​939 NUnit1001 - false positive for arguments with nullable enum parameters
• #​938 [NUnit1031] False positive for nullable structs

v4.11.0: NUnit Analyzers 4.11 - October 28, 2025

Compare Source

NUnit Analyzers 4.11 - October 28, 2025

This release of the NUnit Analyzers includes improvements and fixes related to IDisposable handling and initialization
in SetUp and OneTimeSetUp methods. It also introduces the ability to configure additional methods that should be
treated as SetUp and TearDown methods by the analyzers. This can be done in the .editorconfig, and there are four
configurations for this:

• dotnet_diagnostic.NUnit.additional_setup_methods
• dotnet_diagnostic.NUnit.additional_teardown_methods
• dotnet_diagnostic.NUnit.additional_one_time_setup_methods
• dotnet_diagnostic.NUnit.additional_one_time_teardown_methods

Each configuration accepts a list of method names, separated by commas, semicolons, or spaces. For example:

dotnet_diagnostic.NUnit.additional_setup_methods = CustomSetup, MyInit

As in recent releases, a major part of this work was contributed by @​manfred-brands.

The release contains contributions from the following users (in alphabetical order):

• @​AlisonAMorrison
• @​BodrickLight
• @​cbersch
• @​manfred-brands
• @​mikkelbu
• @​PiotrKlecha
• @​sbe-schleupen

Issues Resolved

Features and Enhancements

• #​921 NUnit1032 - disposals in overridden methods not detected
• #​919 NUnit1032/NUnit3002 - local functions not analyzed
• #​918 NUnit2045 - false positive for inline usings
• #​911 NUnit3002 doesn't recognize the using statement.
• #​910 using declarations not recognized by NUnit2045

Bugs

• #​922 NUnit1001 - false positive for arguments with generic parameters
• #​914 Wrong position of NUnit1001 diagnostic for TestCase with four parameters or more

Tooling, Process, and Documentation

• #​926 chore: Bump NUnit3TestAdapter
• #​908 chore: bump version
• #​885 Bump to NUnit version 4.4 when this is released

VerifyTests/Verify (Verify.NUnit)

v31.7.2

Compare Source

v31.7.1

Compare Source

v31.7.0

Compare Source

v31.6.1

Compare Source

v31.6.0

Compare Source

v31.5.3

Compare Source

v31.5.2

Compare Source

v31.5.1

Compare Source

v31.5.0

Compare Source

v31.4.3

Compare Source

v31.4.2

Compare Source

v31.4.1

Compare Source

v31.4.0

Compare Source

v31.3.0

Compare Source

v31.2.0

Compare Source

v31.1.0

Compare Source

v31.0.5

Compare Source

v31.0.4

Compare Source

v31.0.3

Compare Source

v31.0.2

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.55%. Comparing base (20d5f19) to head (adda4cd).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #838   +/-   ##
=======================================
  Coverage   72.55%   72.55%           
=======================================
  Files          20       20           
  Lines         696      696           
  Branches      146      146           
=======================================
  Hits          505      505           
  Misses        114      114           
  Partials       77       77           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.