Bump NUnit from 3.7.1 to 3.13.2

[dependabot]

Bumps NUnit from 3.7.1 to 3.13.2.

Release notes

Sourced from NUnit's releases.

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

This release adds a .NET Standard 2.0 version of the framework which re-enables most of the features that have been missing in our earlier .NET Standard builds like parallelism, timeouts, directory and path based asserts, etc. It also contains numerous bug fixes and smaller enhancements. We've improved our XML docs, fixed performance issues and added more detail to Multiple Asserts.

This release also contains source-indexed PDB files allowing developers to debug into the NUnit Framework. This allows you to track down errors or see how the framework works.

In order to support the .NET Standard 2.0 version, the NUnit project switched to the new CSPROJ format and now requires Visual Studio 2017 to compile. This only effects people contributing to the project. NUnit still supports building and compiling your tests in older .NET IDEs and NUnit still supports older versions of the .NET Framework back to 2.0. For contributors, NUnit can now compile all supported targets on Windows, Linux and Mac using the Cake command line build.

NUnit 3.9

This release addresses numerous parallelization issues that were introduced in 3.8 when method level parallelization was added. Most of the parallelization issues resolved were tests never completing when using some combinations of parallel tests and ApartmentState not being properly applied to tests in all cases.

... (truncated)

Changelog

Sourced from NUnit's changelog.

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
• 3786 NUnit with dotnet test results in O(n^2) filtering complexity
• 3810 Enable deterministic build
• 3818 AppVeyor failing to build v3.13-dev branch PRs
• 3832 Deploy v3.13-dev branch builds to MyGet

NUnit 3.13.1 - January 31, 2021

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

• 2339 Wrong date format in Ignored TestFixtures
• 3715 FixtureLifeCycle(LifeCycle.InstancePerTestCase) Not working with TestFixtureSource
• 3716 Assembly level FixtureLifeCycle(LifeCycle.InstancePerTestCase) doesn't work
• 3724 Test start and end time should end with Z
• 3726 Assert EqualTo().Within().Seconds does not work with DateTimes in NUnit 3.13
• 3729 AppVeyor builds failing
• 3736 AreEqual.Within throws on failure with non-numeric types
• 3743 Parametrized tests do not respect FixtureLifeCycle.InstancePerTestCase
• 3745 After upgrading to NUnit 3.13.0 the debugger enters NUnit code despite having checked "Enable Just My Code"

NUnit 3.13 - January 7, 2021

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 make 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.

Issues Resolved

• 34 Async testing with F#
• 52 Self-contained item in array causes stack overflow
• 1394 Has.Property cannot see explicit interface implementation properties
• 1491 Add a CLA to the project

... (truncated)

Commits

• 5631b49 Merge pull request #3838 from nunit/release3132
• 18ef24a Fix formatting
• f7c9845 Update changes for 3.13.2 release
• 3606fec Merge pull request #3837 from nunit/backport/2799
• 8008b54 Remove types from test that are not supported in .NET 3.5
• fbae851 Update src/NUnitFramework/framework/Constraints/CollectionTally.cs
• 0384ca6 Update src/NUnitFramework/framework/Constraints/CollectionTally.cs
• 6ec32c7 Update src/NUnitFramework/tests/Constraints/CollectionEquivalentConstraintTes...
• c3814ff Add support for StringCollection
• df63dba Performance improvements comparing equivalence of large collections
• 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]

Superseded by #83.