Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.12.0
->3.13.3
Release Notes
nunit/nunit (NUnit)
v3.13.3
: NUnit 3.13.3This release includes several performance enhancements. @lahma provided a massive speed improvement for large, parametrized test suites. In addition, equivalency tests with large unsortable collections run faster by determining if the collections are sortable before attempting to sort them.
We've added several fixes for .NET 6.0 and we've stopped testing NUnit against .NET Core 2.1 which is now out of support.
There are also several fixes for the new
FixtureLifeCycle
feature and other smaller bug fixes and performance improvements.For more information, please see the complete Framework Release Notes
v3.13.2
This release fixes a new issue with the
FixtureLifeCycle
attribute whereIDisposable
test fixtures were not being disposed properly. As always, @gleb-osokin has been a great help with this new feature.It also fixes a long-standing performance issue with
CollectionAssert.AreEquivalent
and theCollectionEquivalentConstraint
when comparing large collections. The deep comparison that NUnit performs on the two collections will always have a worst case bound of O(n^2) but we have optimized it so that the majority of use cases will be closer to O(n).We've also made significant optimizations to the OR filters for selecting tests using their full name. This dramatically improves test performance for large code bases that use
dotnet test
. Thanks to @pakrym for his help with this.Issues Resolved
v3.13.1
This release addresses several misses with the new
FixtureLifeCycle
attribute, switches to using SourceLink and NuGet snupkg packages for debugging into NUnit from your unit tests. It also addresses issues with the time format of ignored and explicit tests in the test results file.Issues Resolved
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.
This PR has been generated by Mend Renovate. View repository job log here.