NUnit Analyzers 4.15 - September 12, 2026

This release of the NUnit Analyzers adds support for the new numeric types that will
be supported in NUnit 5. The release also improves NUnit1027 by inspecting base fixtures,
and NUnit1028 by supporting IAsyncDisposable.DisposeAsync in addition to the
existing IDisposable.Dispose. The release also includes bug fixes and dependency updates.

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

• @jhavlicek-profinit
• @killergege
• @manfred-brands
• @mikkelbu
• @ngbrown
• @ramonsmits
• @stevenaw
• @uladz-zubrycki

Issues Resolved

Features and Enhancements

• #1019 NUnit1027 does not see [CancelAfter] inherited from a base fixture
• #1017 NU2047 reports failure for new numeric types
• #1001 NUnit1028: Allow DisposeAsync as an exception
• #999 [TestCaseSource] CA1812 suppression

Bugs

• #1013 Use of records crash the NonNullableFieldOrPropertyIsUninitializedSuppressor analyzer
• #998 Assert.EnterMultipleScope clears nullability suppress info

Tooling, Process, and Documentation

• #1005 Bump Microsoft.NET.Test.Sdk from 18.6.0 to 18.7.0
• #996 Bump Microsoft.NET.Test.Sdk from 17.14.1 to 18.6.0
• #993 chore: bump version

NUnit Analyzers 4.14 - June 1, 2026

This release of the NUnit Analyzers adds a new analyzer and associated codefix - NUnit2059 - that helps ensure that
async assertion methods in NUnit version 5 and higher - i.e. Assert.ThrowsAsync, Assert.CatchAsync, and
Assert.DoesNotThrowAsync - have their results observed, as these methods are awaitable from NUnit version 5.

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

• @manfred-brands
• @mikkelbu

Issues Resolved

Features and Enhancements

• #988 Recognize that Assert.ThrowsAsync etc now return a Task that needs awaiting.

Tooling, Process, and Documentation

• #990 Bump cake.tool from 6.1.0 to 6.2.0
• #987 chore: bump version and correct errors in CHANGES.md

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

• @manfred-brands
• @mikkelbu
• @RenderMichael

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

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

• @Dreamescaper
• @manfred-brands
• @mikkelbu
• @nowsprinting
• @philipp-naused
• @stevenaw

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

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

NUnit Analyzers 4.11.1 - October 30, 2025

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

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

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

• @dfev77
• @manfred-brands
• @mikebro
• @mikkelbu

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

NUnit Analyzers 4.9.2 - June 17, 2025

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

• @artificialWave
• @manfred-brands
• @mikkelbu

Issues Resolved

Features and Enhancements

• #892 Assert.EnterMultipleScope not detecting nullability properly

NUnit Analyzers 4.9.1 - June 12, 2025

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

• @MaceWindu
• @manfred-brands
• @mikkelbu

Issues Resolved

Bugs

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