Bump NUnit from 3.9.0 to 3.13.3

[dependabot[bot]]

Bumps NUnit from 3.9.0 to 3.13.3.

Release notes

Sourced from NUnit's releases.

NUnit 3.13.3

This 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

NUnit 3.13.2

This release fixes a new issue with the FixtureLifeCycle attribute where IDisposable 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 the CollectionEquivalentConstraint 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.

For more information, please see the complete Framework Release Notes

NUnit 3.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.

For more information, please see the complete Framework Release Notes

NUnit 3.13

The FixtureLifeCycle attribute has been added to indicate that an instance for a test fixture or all test fixtures in an assembly should be constructed for each test within the fixture or assembly.

This attribute may be applied to a test fixture (class) or to a test assembly. It is useful in combination with the Parallelizable Attribute so that a new instance of a test fixture is constructed for every test within the test fixture. This allows tests to run in isolation without sharing instance fields and properties during parallel test runs. This makes running parallel tests easier because it is easier to make your tests thread-safe.

This release also fixes several issues running tests in .NET 5.0. If your tests target .NET 5.0, we recommend updating to this release.

For more information, please see the complete Framework Release Notes

NUnit 3.12

This release of NUnit finally drops support for .NET 2.0. If your application still targets .NET 2.0, your tests will need to target at least .NET 3.5. Microsoft ended support for .NET 2.0 on July 12, 2011. Microsoft recommends that everyone migrate to at least .NET Framework 3.5 SP1 for security and performance fixes.

This release dramatically improves NUnit support for async tests including returning ValueTask and custom tasks from tests, improved handling of SynchronizationContexts and better exception handling.

The .NET Standard 2.0 version of NUnit continues to gain more functionality that is found in the .NET 4.5 version of the framework like setting the ApartmentState and enabling Timeout on tests.

NUnit 3.11

• More informative assertion messages
• PlatformAttribute is available on .NET Standard 2.0 and now detects .NET Core
• ValuesAttribute now works with nullable types
• Async tests detecting and running Windows Forms or WPF message pumps rather than deadlocking
• Support for UWP 10.0 is back via .NET Standard 1.4

NUnit 3.10.1

Added a namespace to the props file included in the NuGet package to make it compatible with versions of Visual Studio prior to VS 2017.

NUnit 3.10

... (truncated)

Changelog

Sourced from NUnit's changelog.

NUnit 3.13.3 - March 20, 2022

This release includes several performance enhancements. @​lahma provided a massive speed improvement for large parametrized test suites. In addition, quivalency 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.

Issues Resolved

• 2963 Flakey tests in FrameworkControllerTests
• 3643 Assert.Pass(message) produces "reason" in XML-Result
• 3841 Breaking change: Is.SupersetOf with ValueTuple requires IComparable in NUnit 3.13.2
• 3843 IDisposable & InstancePerTestCase: Object created for OneTimeSetUp is not disposed
• 3898 NUnit 3.13.2 : LessThanOrEqualTo fails on a case which should succeed
• 3903 Backport race condition fix (PR 3883)
• 3904 Backport fix for "IDisposable & InstancePerTestCase" (PR 3843)
• 3929 Fix high precision decimal calculations in v3.13 (#3898)
• 3959 Marked 'NUnitEqualityComparer.AreEqual(object, object, Tolerance, bool)' as obsolete
• 3962 Ensure that AfterTest always runs in AfterTestCommand
• 3971 Backport "Add missing [DoesNotReturn] annotations" from #3958
• 3976 Equivalency fallback for non-IComparable types can leave CollectionTally in corrupt state
• 3998 Eagerly determine when a set is unsortable
• 3999 Numeric comparison fails when it should succeed.
• 4000 OverflowException comparing large double values
• 4007 Eagerly detect sortable types for equivalency tests in 3.13.x
• 4030 IsEmpty doesn't work with new .NET6 PriorityQueue
• 4032 Tests won't run with an abstract base class that has a TestCaseFixtureSource
• 4033 Recognized private members in base class for Source attributes
• 4034 Improve method discovery and filtering performance
• 4041 Minimze empty array allocations via centralized helper for pre-net46
• 4043 Stop testing the framework against netcoreapp21 in v3.13 branch
• 4045 Drop netcore2.1 as a target (backport #3986)
• 4058 Remove TopLevel property from ValueMatchFilter

NUnit 3.13.2 - April 27, 2021

This release fixes a new issue with the FixtureLifeCycle attribute where IDisposable 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 the CollectionEquivalentConstraint 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

• 2799 CollectionAssert.AreEquivalent is extremely slow
• 3589 File headers, copyrights, and licenses
• 3773 IDisposable not working with InstancePerTestCase
• 3779 Obsolete AreEqual methods with nullable numeric arguments for 3.13
• 3784 Build the v3.13-dev branch

... (truncated)

Commits

• af8ca8b Merge pull request #4070 from nunit/release-3-13-3
• 380615e Revert sdk version to build on AppVeyor
• d05d9b4 Update copyright year
• 25b376e Update to the latest version of .NET 5
• e2eca31 Changes for the 3.13.3 release
• c32c2e4 Merge pull request #4007 from stevenaw/3998-eager-icomparable-detection
• 8297c3d Merge pull request #4034 from lahma/test-case-perf-improvements-v3
• a19bc73 Merge pull request #4042 from stevenaw/centralize-array-empty
• cf2fa03 implement InFilter.AddToXml
• de83329 move test case from OrFilterTests to InFilterTests
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #199.