Bump NUnit from 2.6.3 to 3.13.1

[dependabot-preview[bot]]

Bumps NUnit from 2.6.3 to 3.13.1.

Release notes

Sourced from NUnit's releases.

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

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.

NUnit 3.8.1

This release fixes two critical regressions in the 3.8 release. The first caused the console runner to crash if you are using test parameters. The second issue caused collection constraints checking for multiple items in a collection to fail.

Issues Resolved

• 2386 Contains.Item() fails for collections in NUnit 3.8
• 2390 Missing value attribute in test parameters setting causes NullReferenceException in console

NUnit 3.8

... (truncated)

Changelog

Sourced from NUnit's changelog.

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
• 1546 NUnitEqualityComparer.GetEquatableGenericArguments should explicitly order arguments
• 1809 Assert.AreEqual fails for Complex on Linux
• 1897 EqualTo().Using() prevents caller from comparing strings to anything else
• 2211 Request: Add support of indexers to the PropertyConstraint
• 2477 Parameterized fixture with Explicit attribute can not be run when selected by name
• 2574 Instance-per-test-case feature
• 2680 Deprecate the DebugWriter class
• 3611 Properties are shown when --explore:nunit3 is run on entire project, but omitted when using the --where clause
• 3054 Don't enforce [Timeout] when debugger is attached
• 3075 Complete RunAsyncAction tests in FrameworkControllerTests
• 3228 Modulo bias is present in Randomizer.NextDecimal(decimal)
• 3240 Automate uploading of test results to Azure Pipelines
• 3243 Azure DevOps does not build release branch
• 3249 Pin GitLink version to speed up Cake script
• 3251 RawInt32() can't use Next since the maximum is always exclusive and it would never return int.MaxValue
• 3252 Timeout of 100 ms in TestTimeoutDoesNotStopCompletion occasionally fails the macOS build
• 3253 Chance of failure in random bias tests is not sufficiently low for CI
• 3256 Building under VS2019
• 3257 Running under mono
• 3259 The type of an Array isn't inferred from properly
• 3264 Test that IRepeatTest only gets attributes via the IMethodInfo interface
• 3275 Enable setting IgnoreUntilDate in TestCaseData.Ignore
• 3279 Improve failure message from UniqueItemsConstraint
• 3282 TimeoutAttribute makes all Assertions count as failure
• 3283 ExecutionContext is flowed between unrelated tests
• 3286 Testing for equality using a predicate throws exception for collections
• 3290 'Good first issue' or 'help wanted' issue count badge
• 3296 ExceptionHelper.GetExceptionMessage(Exception ex) should tolerate exceptions from exceptions
• 3302 Incorrect formatting of failure message if test fails with Assert.Multiple
• 3303 Check type of actual argument using consistent helper method
• 3304 CheckString should not be a generic method
• 3305 Remove unused methods
• 3307 Sporadic GetResultIsNotCalledUntilContinued failure
• 3308 Fix disposal in EnumerablesComparer
• 3309 Simplify code in EventListenerTextWriter
• 3311 Minimal unit of DateTime in the report when Test was started/ended

... (truncated)

Commits

• See full diff 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 use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

Superseded by #73.