Bump NUnit from 3.14.0 to 4.0.0

[dependabot[bot]]

Bumps NUnit from 3.14.0 to 4.0.0.

Release notes

Sourced from NUnit's releases.

NUnit 4.0.0

See release notes and See migration guide

NUnit 4.0.0-beta.1

See release notes and information

Changelog

Sourced from NUnit's changelog.

NUnit 4.0.0 - November 26, 2023

All changes, see release notes

NUnit 4.0.0-beta.1 - October 8, 2023

This release is the first beta release of NUnit 4.0. All changes, see release notes

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.

... (truncated)

Commits

• d91b4cf Merge pull request #4562 from nunit/prepare40-2
• fb95a28 Fixed package description
• 31b3786 Merge pull request #4560 from nunit/prepare40
• 03be54c Fix after comment
• f3b2918 Update README.md
• c2a21bf Update README.md
• 1eb55c0 Update readme
• 8bd4635 Prepare 4.0 release
• ccc776e Merge pull request #4557 from nunit/revert-4222
• 98059ef Switch test condition
• 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 will merge this PR once CI passes on it, as requested by @particularbot.

---

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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions

[particularbot]

@dependabot merge

[dependabot[bot]]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

[dependabot[bot]]

Superseded by #574.