Skip to content

chore: update dependency nunit.analyzers to 4.11.2#656

Merged
olavloite merged 1 commit intogoogleapis:mainfrom
renovate-bot:renovate/nunit.analyzers-4.x
Jan 26, 2026
Merged

chore: update dependency nunit.analyzers to 4.11.2#656
olavloite merged 1 commit intogoogleapis:mainfrom
renovate-bot:renovate/nunit.analyzers-4.x

Conversation

@renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Jan 21, 2026

This PR contains the following updates:

Package Change Age Confidence
NUnit.Analyzers 4.2.04.11.2 age confidence

Release Notes

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

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

v4.10.0: NUnit Analyzers 4.10 - August 9, 2025

Compare Source

NUnit Analyzers 4.10 - August 9, 2025

This release of the NUnit Analyzers contains some minor improvements to NUnit2050, NUnit2056, and NUnit2007 as well
as some improvements to existing tests. Once again, @​manfred-brands was responsible for the majority of the work.

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

Issues Resolved

Bugs

  • #​901 False positive on NUnit2050
  • #​899 NUnit2056 analyzer's code fix removes comments and empty lines above it.
  • #​896 NUnit2007 shouldn't trigger for generic types e.g. typeof(T)

Tooling, Process, and Documentation

  • #​905 NUnit4.4 alpha -> beta changes
  • #​897 chore: Correct typo in NUnit2045.md
  • #​894 Improve tests by adding ↓ to tests were it is missing in the source
  • #​887 chore: bump version

v4.9.2

Compare Source

This release of the NUnit Analyzers extends the NUnit3001 nullability suppressor
to also work in the context of Assert.EnterMultipleScope and other using statements.

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

Issues Resolved

Features and Enhancements

  • #​892 Assert.EnterMultipleScope not detecting nullability properly

v4.9.1

Compare Source

This release of the NUnit Analyzers fixes a problem with the code-fix for translating
Assert.Multiple/Assert.MultipleAsync into the new Assert.EnterMultipleScope format
when the test method already is asynchronous and have a return type different from Task.

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

Issues Resolved

Bugs

  • #​888 Assert.MultipleAsync -> EnterMultipleScope autofix produce invalid code

v4.9.0: NUnit Analyzers 4.9 - June 11, 2025

Compare Source

NUnit Analyzers 4.9 - June 11, 2025

This release of the NUnit Analyzers adds several new analyzers. For the RangeAttribute,
the analyzers now warn about potential issues at runtime.

It also introduces an analyzer and code fix for translating
Assert.Multiple/Assert.MultipleAsync into the new Assert.EnterMultipleScope format, as well
as for converting is T checks into Is.InstanceOf<T>() constraints.

For NUnit2021, the analyzer now respects UsingPropertiesComparer, including enhancements
that will be available in NUnit 4.4.

Finally, this release includes improvements to NUnit2007, NUnit2045, and NUnit4002.
See the list of resolved issues below for more details.

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

Issues Resolved

Features and Enhancements

  • #​880 NUnit2007 could flag typeof() as a constant first parameter
  • #​866 When Assert.Multiple is found, should suggest to convert to Assert.EnterMultipleScope
  • #​865 NUnit 2045 suggest Assert.Multiple, but should suggest Assert.EnterMultipleScope
  • #​857 NUnit2021 Should not raise for UsingPropertiesComparer
  • #​765 Add Rule for converting is T into Is.InstanceOf()
  • #​89 Test the correct usage of the Range attribute

Bugs

  • #​879 NUnit4002 shouldn't trigger for T vs nullable<T> struct types

Tooling, Process, and Documentation

v4.8.1

Compare Source

This release of the NUnit Analyzers fixes a problem with NUnit4002 when applied to comparisons between non-number
types - e.g. strings.

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

Issues Resolved

Bugs

  • #​870 Compilation error caused by exception in an analyzer after updating to v4.8.0

v4.8.0: NUnit Analyzers 4.8 - May 22, 2025

Compare Source

NUnit Analyzers 4.8 - May 22, 2025

This release of the NUnit Analyzers adds a new diagnostic NUnit1034 that checks
whether base TestFixtures are declared as abstract. When a base class is not abstract
it will also be run as a standalone test which is most times not the intention.

The release also contains some fixes to NUnit4002 and Nunit2045.

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

Issues Resolved

Features and Enhancements

  • #​840 Detect incorrect or questionable use of TestFixture inheritance.

Bugs

  • #​862 NUnit.Analyzers doesn't recognize the version of NUnit in use
  • #​856 NUnit4002 shouldn't trigger for unknown types

Tooling, Process, and Documentation

  • #​861 Add missing backticks in NUnit4002.md
  • #​855 chore: bump version

v4.7.0: NUnit Analyzers 4.7 - April 1, 2025

Compare Source

NUnit Analyzers 4.7 - April 1, 2025

The release primarily add another diagnostic NUnit4002 - and associated codefix - to help simplify
EqualTo constraints when the expected value is a simple constant - e.g. true, false, 0, or
default. The release also removes some false positives for Nunit1029.

As tooling contributions the analyzers now build using .NET8.0 and also analyzers and codefixes are
now split into separate projects as only editors should load codefixes.

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

Issues Resolved

Features and Enhancements

  • #​828 Replace Is.EqualTo(default) with Is.Default
  • #​826 Suggest to use Is.Null instead of Is.EqualTo(null)
  • #​824 Use Is.False / Is.True instead of Is.EqualTo

Bugs

  • #​832 False positive for Nunit1029 when only a type argument is use

Tooling, Process, and Documentation

  • #​853 chore: Add NUnit4002.md solution file
  • #​846 chore: Bump NUnit3TestAdapter to version 5
  • #​843 chore(deps): Bump Microsoft.NET.Test.Sdk and Microsoft.NETFramework.ReferenceAssemblies
  • #​838 chore: bump version
  • #​677 Build using .NET8.0 SDK

v4.6.0: NUnit Analyzers 4.6 - January 9, 2025

Compare Source

NUnit Analyzers 4.6 - January 9, 2025

This release contains two improvements: Allowing NUnit1001 to understand DateOnly and TimeOnly parameters in
TestCaseUsage and making NUnit2045 support Assert.EnterMultipleScope (introduced in NUnit version 4.2).

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

Issues Resolved

Features and Enhancements

  • #​820 NUnit1001 compains about DateOnly parameters
  • #​769 Recognized the new Assert.EnterMultipleScope() concept.

Tooling, Process, and Documentation

  • #​829 chore: Bump year to 2025 in copyrights
  • #​823 chore: Bump cake.tool to version 4
  • #​822 chore: Bump NUnit to 4.3.2
  • #​818 chore: Replace "buildstats.info" with "img.shields.io"
  • #​815 chore: bump version

v4.5.0: NUnit Analyzers 4.5 - December 22, 2024

Compare Source

NUnit Analyzers 4.5 - December 22, 2024

The release primarily fixes a problem with the NUnit Analyzers when used with NUnit 4.3.1 - see #​811 for more
information. In additional, we have also added some smaller improvements and bug fixes.

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

Issues Resolved

Features and Enhancements

  • #​811 NUnit2021 ignores cast operation since NUnit 4.3.1
  • #​801 Allow NUnit2005 to recognize Is.Empty

Bugs

  • #​794 AD0001: Occasional InvalidOperationException error in analyzer in IDE

Tooling, Process, and Documentation

  • #​808 chore: Correct typo
  • #​806 Add information about dotnet_diagnostic.NUnit1032.additional_dispose_methods to the docs
  • #​795 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.11.1 to 17.12.0
  • #​793 chore: bump version

v4.4.0: NUnit Analyzers 4.4 - November 13, 2024

Compare Source

NUnit Analyzers 4.4 - November 13, 2024

This release of the NUnit Analyzers adds handling of Assert.IsAssignableFrom/Assert.IsNotAssignableFrom and
Assert.Positive/Assert.Negative. Also insertion of trivia for code fixes for NUnit2007 and NUnit2046
have been improved.

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

Issues Resolved

Features and Enhancements

  • #​790 NUnit.Analyzers 4.3.0 missed an Assert.IsAssignableFrom that caused a build error after upgrading to latest NUnit 4.2.2
  • #​789 NUnit.Analyzers 4.3.0 missed an Assert.Positive that caused a build error after upgrading to latest NUnit 4.2.2

Bugs

  • #​784 Fix trivia for NUnit2046
  • #​783 NUnit2007 doesn't apply trivia correctly

Tooling, Process, and Documentation

  • #​788 chore: Bump NUnit to version 4.2.2
  • #​785 chore(deps): Bump NUnit3TestAdapter from 4.5.0 to 4.6.0
  • #​780 chore(deps): Bump CSharpIsNullAnalyzer from 0.1.495 to 0.1.593
  • #​778 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.10.0 to 17.11.1
  • #​776 chore: bump version
  • #​775 chore: Update release notes

v4.3.0: NUnit Analyzers 4.3 - August 9, 2024

Compare Source

NUnit Analyzers 4.3 - August 9, 2024

This release of the NUnit Analyzers contains some bug fixes to existing analyzers and code fixes - among other
improvements to trivia when using the code fix of NUnit2049.

For new features we now warn against using TestContext.Write as this will be obsolete in NUnit at some point;
NUnit1001 now recognises and check generic TestCase attributes; and we have added a new analyzer and code fix for
simplifying usages of ValuesAttribute.

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

Issues Resolved

Features and Enhancements

  • #​770 Add rule to detect calls to TestContext.Write methods and CodeFix to replace usages with Out.Write
  • #​767 Augment NUnit1001 to recognized and check generic TestCase attributes
  • #​755 New diagnostic: The Values attribute can be simplified.

Bugs

  • #​766 Error when TearDown method is defined in partial test classes - Syntax node is not within syntax tree
  • #​743 NUnit1032 (missing Dispose), if dispose is wrapped in "(… as IDisposable)?.Dispose()"
  • #​739 Null suppression does not work when Assert is fully qualified
  • #​713 Code fix for NUnit2049 places the comma at a wrong place and messes up indentation bug

Tooling, Process, and Documentation

  • #​764 Update the solution file
  • #​761 Update nunit.analyzers.nuspec to specify that NUnit.Analyzers v4 is intended to be used with NUnit 4.
  • #​756 error NUnit1032 is incorrect when InstancePerTestCase and constructor is used to initialize IDisposible
  • #​741 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.9.0 to 17.10.0 in /src
  • #​737 Update NUnit2013.md to fix code block
  • #​736 chore: bump version
  • #​734 Why dropping composite message formatting support also for Assert.Pass/Fail/... where there are no actual and constraint parameters?

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 this update again.


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

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

@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jan 21, 2026
@gemini-code-assist
Copy link

Summary of Changes

Hello @renovate-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the NUnit.Analyzers dependency to its latest major version, 4.11.2. This update integrates a comprehensive suite of new static analysis rules and code fixes, enhancing the project's ability to detect potential issues, enforce best practices, and improve the overall quality and maintainability of NUnit test code. The upgrade ensures the project benefits from the most current diagnostic capabilities for NUnit tests.

Highlights

  • Major Dependency Upgrade: The NUnit.Analyzers package has been updated from version 3.9.0 to 4.11.2, encompassing all releases within the v4 series. This upgrade brings a significant number of new features, enhancements, and bug fixes.
  • New Analyzers and Code Fixes: Several new analyzers and corresponding code fixes have been introduced. These include simplifying Is.EqualTo constraints (e.g., to Is.Null, Is.True), converting Assert.Multiple to Assert.EnterMultipleScope, detecting issues with RangeAttribute, and identifying unnecessary lambda expressions in asserts.
  • Enhanced Static Analysis: Existing analyzers have been improved to provide better nullability suppression (including for Assume.That and the null-forgiving operator), more accurate IDisposable handling in SetUp/OneTimeSetUp methods, and correct recognition of DateOnly/TimeOnly parameters in TestCaseUsage.
  • Configuration Flexibility: The analyzers now allow configuration of additional SetUp and TearDown methods via .editorconfig settings, providing greater flexibility for custom test setups.
  • Bug Fixes and Stability: Numerous bugs have been addressed, including false positives, regressions in code fixes (e.g., for Assert.MultipleAsync to EnterMultipleScope), and improved handling of trivia insertion for code fixes.
  • Dropped Support for Older Visual Studio: Version 4 of the NUnit Analyzers drops support for Visual Studio releases older than Visual Studio 2019 16.3.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the NUnit.Analyzers package to version 4.11.2. While keeping dependencies up-to-date is good practice, this major version upgrade introduces a compatibility issue. NUnit.Analyzers v4.x requires NUnit v4.x, but the projects are still using NUnit v3.14.0. This mismatch can lead to incorrect behavior from the analyzers. I've left comments in the project files recommending that the NUnit package also be upgraded to a compatible version to resolve this.

@renovate-bot renovate-bot force-pushed the renovate/nunit.analyzers-4.x branch 3 times, most recently from 10e7a05 to eef0817 Compare January 26, 2026 11:14
@renovate-bot renovate-bot changed the title chore: update dependency nunit.analyzers to v4 chore: update dependency nunit.analyzers to 4.11.2 Jan 26, 2026
@renovate-bot renovate-bot force-pushed the renovate/nunit.analyzers-4.x branch from eef0817 to cc45129 Compare January 26, 2026 17:06
@olavloite olavloite merged commit 668d207 into googleapis:main Jan 26, 2026
17 checks passed
@renovate-bot renovate-bot deleted the renovate/nunit.analyzers-4.x branch January 26, 2026 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kokoro:force-run Add this label to force Kokoro to re-run the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants