nunit/nunit.analyzers (NUnit.Analyzers)
### [`v4.3.0`](https://togithub.com/nunit/nunit.analyzers/releases/tag/4.3.0): NUnit Analyzers 4.3 - August 9, 2024
[Compare Source](https://togithub.com/nunit/nunit.analyzers/compare/4.2.0...4.3.0)
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):
- [@andrewimcclement](https://togithub.com/andrewimcclement)
- [@Bartleby2718](https://togithub.com/Bartleby2718)
- [@DrPepperBianco](https://togithub.com/DrPepperBianco)
- [@KaiBNET](https://togithub.com/KaiBNET)
- [@maettu-this](https://togithub.com/maettu-this)
- [@manfred-brands](https://togithub.com/manfred-brands)
- [@mikkelbu](https://togithub.com/mikkelbu)
- [@RenderMichael](https://togithub.com/RenderMichael)
- [@SeanKilleen](https://togithub.com/SeanKilleen)
- [@trampster](https://togithub.com/trampster)
Issues Resolved
Features and Enhancements
- [#770](https://togithub.com/nunit/nunit.analyzers/issues/770) Add rule to detect calls to TestContext.Write methods and CodeFix to replace usages with Out.Write
- [#767](https://togithub.com/nunit/nunit.analyzers/issues/767) Augment NUnit1001 to recognized and check generic TestCase attributes
- [#755](https://togithub.com/nunit/nunit.analyzers/issues/755) New diagnostic: The Values attribute can be simplified.
Bugs
- [#766](https://togithub.com/nunit/nunit.analyzers/issues/766) Error when TearDown method is defined in partial test classes - Syntax node is not within syntax tree
- [#743](https://togithub.com/nunit/nunit.analyzers/issues/743) NUnit1032 (missing Dispose), if dispose is wrapped in "(… as IDisposable)?.Dispose()"
- [#739](https://togithub.com/nunit/nunit.analyzers/issues/739) Null suppression does not work when Assert is fully qualified
- [#713](https://togithub.com/nunit/nunit.analyzers/issues/713) Code fix for NUnit2049 places the comma at a wrong place and messes up indentation bug
Tooling, Process, and Documentation
- [#764](https://togithub.com/nunit/nunit.analyzers/issues/764) Update the solution file
- [#761](https://togithub.com/nunit/nunit.analyzers/issues/761) Update nunit.analyzers.nuspec to specify that NUnit.Analyzers v4 is intended to be used with NUnit 4.
- [#756](https://togithub.com/nunit/nunit.analyzers/issues/756) error NUnit1032 is incorrect when InstancePerTestCase and constructor is used to initialize IDisposible
- [#741](https://togithub.com/nunit/nunit.analyzers/issues/741) chore(deps): Bump Microsoft.NET.Test.Sdk from 17.9.0 to 17.10.0 in /src
- [#737](https://togithub.com/nunit/nunit.analyzers/issues/737) Update NUnit2013.md to fix code block
- [#736](https://togithub.com/nunit/nunit.analyzers/issues/736) chore: bump version
- [#734](https://togithub.com/nunit/nunit.analyzers/issues/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: Enabled.
♻ 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 this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
4.2.0->4.3.0Release Notes
nunit/nunit.analyzers (NUnit.Analyzers)
### [`v4.3.0`](https://togithub.com/nunit/nunit.analyzers/releases/tag/4.3.0): NUnit Analyzers 4.3 - August 9, 2024 [Compare Source](https://togithub.com/nunit/nunit.analyzers/compare/4.2.0...4.3.0) 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): - [@andrewimcclement](https://togithub.com/andrewimcclement) - [@Bartleby2718](https://togithub.com/Bartleby2718) - [@DrPepperBianco](https://togithub.com/DrPepperBianco) - [@KaiBNET](https://togithub.com/KaiBNET) - [@maettu-this](https://togithub.com/maettu-this) - [@manfred-brands](https://togithub.com/manfred-brands) - [@mikkelbu](https://togithub.com/mikkelbu) - [@RenderMichael](https://togithub.com/RenderMichael) - [@SeanKilleen](https://togithub.com/SeanKilleen) - [@trampster](https://togithub.com/trampster) Issues Resolved Features and Enhancements - [#770](https://togithub.com/nunit/nunit.analyzers/issues/770) Add rule to detect calls to TestContext.Write methods and CodeFix to replace usages with Out.Write - [#767](https://togithub.com/nunit/nunit.analyzers/issues/767) Augment NUnit1001 to recognized and check generic TestCase attributes - [#755](https://togithub.com/nunit/nunit.analyzers/issues/755) New diagnostic: The Values attribute can be simplified. Bugs - [#766](https://togithub.com/nunit/nunit.analyzers/issues/766) Error when TearDown method is defined in partial test classes - Syntax node is not within syntax tree - [#743](https://togithub.com/nunit/nunit.analyzers/issues/743) NUnit1032 (missing Dispose), if dispose is wrapped in "(… as IDisposable)?.Dispose()" - [#739](https://togithub.com/nunit/nunit.analyzers/issues/739) Null suppression does not work when Assert is fully qualified - [#713](https://togithub.com/nunit/nunit.analyzers/issues/713) Code fix for NUnit2049 places the comma at a wrong place and messes up indentation bug Tooling, Process, and Documentation - [#764](https://togithub.com/nunit/nunit.analyzers/issues/764) Update the solution file - [#761](https://togithub.com/nunit/nunit.analyzers/issues/761) Update nunit.analyzers.nuspec to specify that NUnit.Analyzers v4 is intended to be used with NUnit 4. - [#756](https://togithub.com/nunit/nunit.analyzers/issues/756) error NUnit1032 is incorrect when InstancePerTestCase and constructor is used to initialize IDisposible - [#741](https://togithub.com/nunit/nunit.analyzers/issues/741) chore(deps): Bump Microsoft.NET.Test.Sdk from 17.9.0 to 17.10.0 in /src - [#737](https://togithub.com/nunit/nunit.analyzers/issues/737) Update NUnit2013.md to fix code block - [#736](https://togithub.com/nunit/nunit.analyzers/issues/736) chore: bump version - [#734](https://togithub.com/nunit/nunit.analyzers/issues/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: Enabled.
♻ 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.