Skip to content

chore(deps): update .net test stack#66

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/net-test-stack
Open

chore(deps): update .net test stack#66
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/net-test-stack

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Nov 1, 2025

This PR contains the following updates:

Package Change Age Confidence
Microsoft.NET.Test.Sdk 18.0.118.5.1 age confidence
NUnit.Analyzers 4.10.04.13.0 age confidence

Release Notes

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

v18.5.1

What's Changed

Full Changelog: microsoft/vstest@v18.5.0...v18.5.1

v18.5.0

⚠️ Unlisted on Nuget, because of #​15718

What's Changed

Full Changelog: microsoft/vstest@v18.4.0...v18.5.0

v18.4.0

What's Changed
New Contributors

Full Changelog: microsoft/vstest@v18.3.0...v18.4.0

v18.3.0

What's Changed
Internal fixes and updates
New Contributors
nunit/nunit.analyzers (NUnit.Analyzers)

v4.13.0: NUnit Analyzers 4.13 - May 2, 2026

Compare Source

NUnit Analyzers 4.13 - May 2, 2026

This release of the NUnit Analyzers updates analyzer handling for the NUnit 4.6 API change that replaces
ActualValueDelegate<> with Func<> - see nunit/nunit#4824 for more information.
Analyzers now also consider the return type of Func<> in assertions. The release also includes one bug fix and
some dependency updates.

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

Issues Resolved

Features and Enhancements

  • #​982 Recognized Func<T> return values

Bugs

  • #​968 Whitespace issue in Does.Contain fixer when assert spans multiple lines

Tooling, Process, and Documentation

  • #​985 chore: Bump year to 2026 in copyrights
  • #​978 Bump cake.tool from 6.0.0 to 6.1.0
  • #​976 chore: Correct documentation
  • #​975 chore: bump version
  • #​956 Bump cake.tool from 4.0.0 to 6.0.0

v4.12.0: NUnit Analyzers 4.12 - March 3, 2026

Compare Source

NUnit Analyzers 4.12 - March 3, 2026

This release of the NUnit Analyzers improves NUnit1029 to account for TestCaseSource
support for params and optional arguments. It also introduces a new analyzer for incorrect
usage of Is.Not.Null.Or.Empty, fixes regressions in NUnit2005 and NUnit2055, and updates
NUnit package dependencies.

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

Issues Resolved

Features and Enhancements

  • #​957 Relax NUnit1029 for TestCaseSource where method accepts a single "params" array
  • #​189 Warning when Is.Not.Null.Or.Empty used

Bugs

  • #​953 Code fix for NUnit2055 can generate invalid code for classic asserts
  • #​952 Code fix for NUnit2005 tries to use Is.Empty constraint on incompatible types.

Tooling, Process, and Documentation

  • #​973 chore: Bump NUnit version
  • #​970 chore: Bump NUnit to version 4.5.0
  • #​967 Fix note about works with Unity Test Framework
  • #​937 chore: bump version

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):

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):

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):

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

Configuration

📅 Schedule: (UTC)

  • 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 is behind base branch, 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.

@renovate renovate Bot force-pushed the renovate/net-test-stack branch from 3825867 to 79ed39c Compare November 3, 2025 02:47
@renovate renovate Bot changed the title chore(deps): update dependency nunit.analyzers to 4.11.0 chore(deps): update dependency nunit.analyzers to 4.11.1 Nov 3, 2025
@renovate renovate Bot force-pushed the renovate/net-test-stack branch from 79ed39c to 6c9d52c Compare November 5, 2025 16:54
@renovate renovate Bot changed the title chore(deps): update dependency nunit.analyzers to 4.11.1 chore(deps): update dependency nunit.analyzers to 4.11.2 Nov 5, 2025
@renovate renovate Bot force-pushed the renovate/net-test-stack branch 3 times, most recently from 7c948ce to 980964e Compare November 30, 2025 00:03
@renovate renovate Bot force-pushed the renovate/net-test-stack branch 2 times, most recently from 93abdfb to 6a180be Compare December 20, 2025 21:33
@renovate renovate Bot force-pushed the renovate/net-test-stack branch from 6a180be to 903d18d Compare February 27, 2026 14:10
@renovate renovate Bot changed the title chore(deps): update dependency nunit.analyzers to 4.11.2 chore(deps): update .net test stack Feb 27, 2026
@renovate renovate Bot force-pushed the renovate/net-test-stack branch from 903d18d to 9eeab67 Compare March 10, 2026 17:13
@renovate renovate Bot force-pushed the renovate/net-test-stack branch from 9eeab67 to 7c8b887 Compare April 10, 2026 09:29
@renovate renovate Bot force-pushed the renovate/net-test-stack branch from 7c8b887 to 20e49eb Compare May 1, 2026 18:48
@renovate renovate Bot force-pushed the renovate/net-test-stack branch from 20e49eb to 1335118 Compare May 5, 2026 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants