Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency NUnit.Analyzers to v4 #55

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 2, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
NUnit.Analyzers 3.3.0 -> 4.4.0 age adoption passing confidence

Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.


Release Notes

nunit/nunit.analyzers (NUnit.Analyzers)

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?

v4.2.0: NUnit Analyzers 4.2 - April 24, 2024

Compare Source

NUnit Analyzers 4.2 - April 24, 2024

This release of the Analyzers extends NUnit2050 to also cover Assume and Nunit1032 to consider dispose of a type
having explicit interface implementation. Furthermore, named parameters are now handled correctly codefixes for
classical asserts, and NUnit2010 improves the logic for determining Equals methods.

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

Issues Resolved

Features and Enhancements

  • #​731 Add test for wrapping conditional expression in parenthesis for NUnit2050
  • #​720 Replace UpdateStringFormatToFormattableString with String.Format
  • #​719 NUnit2050 should cover Assume
  • #​710 Nunit1032 - consider dispose of a type having explicit interface implementation

Bugs

  • #​728 NUnit2010 - do not consider Equals call if it doesn't override Object.Equals
  • #​712 [bug] Code fix for NUnit2005 does not correctly fix Assert.AreEqual if named parameters are used in unexpected order

Tooling, Process, and Documentation

  • #​733 Missing full stops added to NUnit2050
  • #​722 Use Markdown for CHANGES
  • #​708 chore: bump-version

v4.1.0: NUnit Analyzers 4.1 - March 16, 2024

Compare Source

NUnit Analyzers 4.1 - March 16, 2024

This release of the Analyzers extends the suppression of nullable warnings to also respect assumptions -
expressed via Assume.That. Also nullable warnings are suppressed even in the context of the
null-forgiving operator !, and NUnit2010 is extended to also cover is pattern expressions - e.g.
is null and more general integer patterns as is < 0 or >= 1.

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

Issues Resolved

Features and Enhancements

  • #​693 Possibly Null Reference Warning should be suppressed for Assume
  • #​691 Extent rule NUnit2010 to detect 'is null'
  • #​679 Null suppression doesn't work when the body has a null suppression

Bugs

  • #​700 CodeFix for Assert with null message causes ambiguous code.
  • #​689 Incorrect constraint model transformation for named parameters

Tooling, Process, and Documentation

  • #​697 chore: Bump NUnit to version 4.1.0
  • #​694 Switch to using license expression
  • #​690 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.8.0 to 17.9.0
  • #​687 chore: Update release notes

v4.0.1: NUnit Analyzers 4.0.1 - February 1, 2024

Compare Source

NUnit Analyzers 4.0.1 - February 1, 2024

Small release that fixes a problem with the 4.0 release when combining TestCaseSource and CancelAfter.

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

Issues Resolved

Bugs

  • #​685 error NUnit1029: The TestCaseSource provides '1' parameter(s), but the Test method expects '1' parameter(s)

Tooling, Process, and Documentation

v4.0.0: NUnit Analyzers 4.0

Compare Source

NUnit Analyzers 4.0 - January 27, 2024

Version 4 of the NUnit analyzers drops the support for older releases of Visual Studio. I.e.
releases of Visual Studio that are older than Visual Studio 2019 16.3. In addition, this release
contains various bug fixes to existing analyzers, support of the CancelAfterAttribute
that was introduced in NUnit 4, and extends the codefix for NUnit2007 to also work when
.Within is used.

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

Issues Resolved

Features and Enhancements

  • #​669 NUnit2007 does not provide codefix when .Within is used
  • #​609 Drop support for VS before 2019

Bugs

  • #​663 NUnit1027 fired when CancellationToken and [CancelAfter] is given
  • #​659 NUnit1032 throws an exception in a specific configuration
  • #​656 NUnit1028 warns about overridden methods
  • #​635 ArgumentException in DisposeFieldsAndPropertiesInTearDownAnalyzer

Tooling, Process, and Documentation

  • #​676 chore: markdownlint-cli2-config is removed use flag instead
  • #​668 chore(deps): Bump StyleCop.Analyzers.Unstable from 1.2.0.507 to 1.2.0.556
  • #​662 chore: Bump NUnit 4 to version 4.0.1
  • #​660 chore: Bump to NUnit 4
  • #​654 chore: Bump version
  • #​630 Update NUnit Analyzer docs to respect 120-character docs rule documentation
  • #​508 Restore "File version" and "Product version" in analyzer dlls

v3.10.0: NUnit Analyzers 3.10 (and 2.10)

Compare Source

NUnit Analyzers 3.10 (and 2.10) - November 27, 2023

This release adds a couple of improvements to the analyzers:

  • Check that users don't accidentally specify CallerArgumentExpression parameters
  • Relax analyzers for added support for IAsyncEnumerable on *Source attributes

These improvements extend the functionality in the beta that added support for NUnit 4 and
for migrating to NUnit 4. Especially, the handling of the movement of classic asserts into a new namespace
NUnit.Framework.Legacy and of the improved assert result messages - for more information see
https://docs.nunit.org/articles/nunit/Towards-NUnit4.html. The analyzers can help updating the
classic assert and fix the assert messages.

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

Issues Resolved

Features and Enhancements

  • #​639 Rule to check users don't accidentally specify CallerArgumentExpression parameters
  • #​634 Relax analyzers for added support for IAsyncEnumerable on *Source attributes

Tooling, Process, and Documentation

  • #​648 chore: Skip branch builds on PRs
  • #​644 chore: Update release notes for 3.10 beta
  • #​429 Drop the VSIX project

v3.9.0: NUnit Analyzers 3.9 (and 2.9)

Compare Source

NUnit Analyzers 3.9 (and 2.9) - October 27, 2023

This release contains bugfixes to NUnit2045 - Use Assert.Multiple - and NUnit1032 -
An IDisposable field/property should be Disposed in a TearDown method - and corrects
a StackOverflowException when tests calls methods recursively.

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

Issues Resolved

Bugs

  • #​614 NUnit2045 does not respect lambda captures
  • #​607 NUnit1032 false positive when test class is static
  • #​602 Bug: StackOverflowException when test calls recursive method in 3.7.

v3.8.0: NUnit Analyzers 3.8 (and 2.8)

Compare Source

NUnit Analyzers 3.8 (and 2.8) - September 25, 2023

This release contains a fix to the WithinUsageAnalyzer and handling of false duplicates when
combining NUnit1032 - An IDisposable field/property should be Disposed in a TearDown method -
with LifeCycle.InstancePerTestCase.

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

Issues Resolved

Features and Enhancements

  • #​595 NUnit1032 false positive in LifeCycle.InstancePerTestCase test fixture using constructor

Bugs

  • #​596 WithinUsageAnalyzer threw an exception of type 'System.IndexOutOfRangeException'

Tooling, Process, and Documentation

  • #​598 Update NUnit1032.md to fix typo Dipose -> Dispose.

v3.7.0: NUnit Analyzers 3.7 (and 2.7)

Compare Source

NUnit Analyzers 3.7 (and 2.7) - September 16, 2023

This release contains a lot of improvements and corrections to the supression of non-nullable fields and properties
that are assigned in setup methods (and not in constructors). We have also added suppression of:

  • CA1812 - Avoid uninstantiated internal classes - on test classes
  • CA1001 - Types that own disposable fields should be disposable - when disposed is called in TearDown methods

The release also contain some improvements to the performance of the analyzers by avoid repeated calls to
GetTypeByMetadataName. Also ValuesAttribute is now also handled by the analyzer in a similar manner as TestCaseAttribute.
Most of the work done in this release have either been driven by or made by @​manfred-brands.

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

Issues Resolved

Features and Enhancements

  • #​585 NonNullableFieldOrPropertyIsUninitializedSuppressor doesn't check async methods called from SetUp
  • #​582 NonNullableFieldOrPropertyIsUninitializedSuppressor does not detect assignments in try/finally blocks
  • #​569 Added a suppressor when CA1812 fires on NUnit Test classes.
  • #​568 Feature request: suppress CA1001 when Dispose is called in the TearDown method
  • #​561 NUnit2021 error shown when comparing Uri and string
  • #​548 Use RegisterCompilationStartAction to avoid repeated calls to GetTypeByMetadataName
  • #​542 Allow the *Source Analyzers to permit Task
  • #​462 DiagnosticsSuppress does not suppress CS8634
  • #​344 Add a rule informing that .Within is not valid for non-numeric types.
  • #​52 Reuse TestCaseAttribute logic for ValuesAttribute improvement

Bugs

  • #​587 Buggy interaction between the Assert.Multiple fixer and null reference suppression
  • #​580 False positive for WithinUsageAnalyzer
  • #​559 FP NUnit1001: CustomTypeConverters could convert from anything
  • #​549 Code Fix for NUnit2010 on Ref Structs Creates CS0306
  • #​541 [NUnit2045] Incorrect refactoring
  • #​535 DiagnosticSuppressor doesn't suppress values passed as arguments
  • #​534 QuickFix for Assert.Multiple looses white space before and comments after bug

Tooling, Process, and Documentation

  • #​579 chore: Bump Microsoft.NET.Test.Sdk
  • #​578 chore(deps): Bump Microsoft.CodeAnalysis.NetAnalyzers
  • #​573 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.7.0 to 17.7.1
  • #​571 chore(deps): Bump System.Collections.Immutable from 6.0.0 to 7.0.0
  • #​567 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.6.3 to 17.7.0
  • #​566 Update CONTRIBUTING.md to fix link to MS documentation.
  • #​560 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.6.2 to 17.6.3
  • #​558 chore(deps): Bump StyleCop.Analyzers.Unstable from 1.2.0.435 to 1.2.0.507
  • #​557 chore(deps): Bump Microsoft.CodeAnalysis.NetAnalyzers from 7.0.1 to 7.0.3
  • #​556 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.6.1 to 17.6.2
  • #​553 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.6.0 to 17.6.1
  • #​551 chore(deps): Bump NUnit3TestAdapter from 4.4.2 to 4.5.0
  • #​547 chore(deps): Bump CSharpIsNullAnalyzer from 0.1.300 to 0.1.495
  • #​543 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.5.0 to 17.6.0
  • #​531 Markdown fixes

v3.6.1: NUnit Analyzers 3.6.1 (and 2.6.1) - March 10, 2023

Compare Source

NUnit Analyzers 3.6.1 (and 2.6.1) - March 10, 2023

This release of the NUnit Analyzers contain a single bug fix and some updates of dependencies.
The bug fix removes a false from NUnit1030 - "The type of parameter provided by the TestCaseSource
does not match the type of the parameter in the Test method" - when using TestCaseParameters.

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

Issues Resolved

Bugs

  • #​523 False positive for NUnit1030 with TestCaseParameters bug

Tooling, Process, and Documentation

  • #​528 chore(deps): Bump NUnit3TestAdapter from 4.4.0 to 4.4.2
  • #​527 chore(deps): Bump NUnit3TestAdapter from 4.3.1 to 4.4.0
  • #​522 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.4.1 to 17.5.0

v3.6.0: NUnit Analyzers 3.6 (and 2.6)

Compare Source

NUnit Analyzers 3.6 (and 2.6) - February 21, 2023

This release of the NUnit Analyzers improves on the analysis of nullable reference types - in particular
in case of null coalescing operator and tuple deconstruction assignments.

The release also adds two new diagnostics for the TestCaseSource attribute. The diagnostics examines the test data returned
from the TestCaseSource:

  • NUnit1029 - The number of parameters provided by the TestCaseSource does not match the number of parameters in the Test method
  • NUnit1030 - The type of parameter provided by the TestCaseSource does not match the type of the parameter in the Test method

In addition, the release also contains some bug fixes to existing analyzers, and we have added a GitHub Actions workflow
and status badge.

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

The majority of the code contributions were provided by @​manfred-brands.

Issues Resolved

Features and Enhancements

  • #​503 DiagnosticsSuppressor doesn't suppress null coalescing operator
  • #​499 DiagnosticSuppressor doesn't detect tuple deconstruction assignments
  • #​442 Analyzer for TestCaseSource does not check Test method parameters

Bugs

  • #​509 Giving TestCaseAttribute an explicit decimal for a parameter that is a decimal gives a Nunit 1001 error
  • #​496 NUnit2045 code-fix does not correctly lift asynchronous assertions into Assert.Multiple
  • #​475 Code Fix for NUnit2010 on Ref Structs Creates CS1503

Tooling, Process, and Documentation

  • #​519 chore: Update year to 2023
  • #​518 fix: Correct MSDN link on new pages
  • #​516 Replace link to ruleset docs
  • #​507 chore: Add Github Action build status badge
  • #​500 Fix path to global.json
  • #​497 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.3.2 to 17.4.1
  • #​489 Add note about works with unity3d
  • #​487 chore(deps): Bump NUnit3TestAdapter from 4.2.1 to 4.3.0
  • #​486 chore: Bump version to 3.6 (2.6)
  • #​476 [add] GitHub Actions workflow for running test

v3.5.0: NUnit Analyzers 3.5 (and 2.5)

Compare Source

NUnit Analyzers 3.5 (and 2.5) - October 23, 2022

This release of the NUnit Analyzers only fixes the casing in a file name in the nuget file as nuget upload validation failed.

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

Issues Resolved

Tooling, Process, and Documentation

  • #​484 chore: Bump version to 3.5 (2.5)
  • #​483 chore: NuGet.org validation is case sensitive

Configuration

📅 Schedule: Branch creation - "on the 1st through 7th day of the month" in timezone America/Los_Angeles, 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.

@renovate renovate bot added the bot label Feb 2, 2024
@renovate renovate bot force-pushed the renovate/nunit.analyzers-4.x branch from b716b0a to d51ddb6 Compare March 17, 2024 11:55
@renovate renovate bot force-pushed the renovate/nunit.analyzers-4.x branch from d51ddb6 to 5708197 Compare April 26, 2024 20:46
@renovate renovate bot force-pushed the renovate/nunit.analyzers-4.x branch from 5708197 to 8539fae Compare August 10, 2024 23:56
@renovate renovate bot force-pushed the renovate/nunit.analyzers-4.x branch from 8539fae to 9150308 Compare November 14, 2024 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants