Bump NUnit from 2.6.3 to 3.14.0

[dependabot]

Updated NUnit from 2.6.3 to 3.14.0.

Release notes

Sourced from NUnit's releases.

3.14.0

See release notes

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

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

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

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

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.

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

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.

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.

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.

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

3.8

This release removes several methods and attributes that were marked obsolete in the
original 3.0 release. Support for iOS and Android has been improved.

An issue that caused unit tests to run slower was addressed as was a bug that prevented
the use of Assert.Multiple in async code.

The Order attribute can now also be applied to the class level to set the order
that test fixtures will be run.

Issues Resolved

• 345 Order of Fixture Execution
• 1151 Include differences in output for Is.EquivalentTo
• 1324 Remove CollectionContainsConstraint
• 1670 Attaching files to the test result
• 1674 InRange-Constraint must work with object
• 1851 TestCaseSource unable to pass one element byte array
• 1996 Timeout does not work if native code is running at the time
• 2004 Has.One as synonym for Has.Exactly(1).Items
• 2062 TestCaseSource attribute causes test to pass when source is not defined
• 2144 Allow option on RandomAttribute to produce distinct values
• 2179 Some NUnit project's tests fail on systems with CultureInfo other than en
• 2195 Contains.Substring with custom StringComparison
• 2196 Expose ParallelizableAttribute (and other attribute) constructor arguments as properties
• 2201 Invalid platform name passed to PlatformAttribute should mark test NotRunnable
• 2208 StackFIlter trims leading spaces from each line
• 2213 SetCultureAttribute: CultureInfo ctor should use default culture settings
• 2217 Console runner performance varies wildly depending on environmental characteristics
• 2219 Remove Obsolete Attributes
• 2225 OneTimeTearDown and Dispose Ordering
• 2237 System.Runtime.Loader not available for iOS/Android
• 2242 Running tests directly should never surface a NullReferenceException
• 2244 Add KeyValuePair<TKey, TValue> to the default formatters
• 2251 Randomizer.NextGuid()
• 2253 Parallelizable(ParallelScope.Fixtures) doesn't work on a TestFixture
• 2254 EqualTo on ValueTuple with Nullable unexpected
• 2261 When an assembly is marked with ParallelScope.None and there are Parallelizable tests Nunit hangs
• 2269 Parallelizable and NonParallelizable attributes on setup and teardown silently ignored
• 2276 Intermittent test failures in Travic CI: TestContextTests
• 2281 Add type constraint for Throws and any method requiring Exception
• 2288 Killing thread cancels test run
• 2292 Is.Ordered.By() with a field throws NullReferenceException
• 2298 Write TestParametersDictionary to xml result file in readable format
• 2299 NUnitLite NuGet package no longer installs NUnit NuGet package
• 2304 Revert accidental doc removal
• 2305 Correct misprint ".con" -> ".com"
• 2312 Prevent crash on invalid --result parsing in NUnitLite
• 2313 Incorrect xmldoc on RetryAttribute
• 2332 Update build script to use NUnitConsoleRunner v3.7.0
• 2335 Execute OneTimeTearDown as early as possible when running fixtures in parallel
  ... (truncated)

3.7.1

This is a hotfix release that addresses occasional hangs when using test parallization and fixes crashes in NCrunch prior to version 3.9.

3.7

This release of NUnit expands on parallel test execution to allow test methods to be run in parallel. Please see the Parallelizable Attribute for more information.

NUnit 3.7 also drops the Portable build of the framework and replaces it with a .NET Standard 1.3 version to complement the .NET Standard 1.6 version. This change enables several constraints and other features in the .NET Standard builds that weren't available in portable like Path and Directory based asserts.

The AssertionHelper class has been deprecated because it is seldom used and has not received any of the updates that Asserts and Constraints receive. If your code is using the AssertionHelper class, we recommend that you migrate your asserts.

3.6.1

This is a hotfix release of the framework that addresses critical issues found in the 3.6 release.

Issues Resolved

• 1962 A Theory with no data passes
• 1986 NUnitLite ignores --workers option
• 1994 NUnitLite runner crashing when --trace is specified
• 2017 Two NUnit project's tests fail on systems with comma decimal mark settings
• 2043 Regression in 3.6.0 when catching AssertionException

3.6

This release of the framework no longer includes builds for Compact Framework or for SilverLight, but adds a .NET Standard 1.6 build. If anyone still using Compact Framework or SilverLight and would like to continue development on those versions of the framework, please contact the NUnit team.

Framework

• .NET Standard 1.6 is now supported
• Adds support for Multiple Assert blocks
• Added the --params option to NUnitLite
• Theories now support Nullable enums
• Improved assert error messages to help differentiate differences in values
• Added warnings with Warn.If(), Warn.Unless() and Assert.Warn()
• Enabled Path, File and Directory Asserts/Contraints for .NET Core testing
• Added NonTestAssemblyAttribute for use by third-party developers to indicate that their assemblies reference the NUnit framework, but do not contain tests

See the release notes for a complete list of changes.

3.5

This is the first version of NUnit where the framework will be released separately from the
console runner, engine and other extensions. From this point forward, the NUnit Framework will be
released on its own schedule that is not bound to that of any other NUnit project and version numbers
may diverge over time.

This is also the first release where the NUnit Framework will not be included in the installer. Only
the console runner, engine and extensions will be available as an MSI installer. We recommend that you
use the NUnit NuGet packages for the framework, but a ZIP file with the binaries will also be available.

Framework

• Added Assert.Zero and Assert.NotZero methods
• Tests with a Timeout will no longer timeout while you are debugging

See the release notes for a complete list of changes.

3.4.1

Console Runner

• A new option, --list-extensions, will display all the engine extensions that
  have been installed by the engine.

Issues Resolved

• 1623 NUnit 3.4 is not integrated with TeamCity
• 1626 NUnit.ConsoleRunner is not picking up NUnit.Extension.NUnitV2ResultWriter
• 1628 Agent's process stays in memory when it was failed to unload AppDomain
• 1635 Console option to list loaded extensions

3.4

Framework

• Improvements in comparing equality using IEquatable
• Test case names will only be truncated if the runner requests it or it is overridden on the command line
  with the --test-name-format option
• The .NET 2.0 version of the framework now includes LINQ. If your tests target .NET 2.0, you can now use
  LINQ queries in your tests

Engine

• The TeamCity event listener has been separated out into an engine extension
• Fixed numerous issues around thread safety of parallel test runs
• Additional fixes to reduce memory usage
• Fixes for Mono 4.4

Console Runner

• There is a new --params command line option that allows you to pass parameters to your tests
  which can be retrieved using TestContext.Parameters
• Another new command line option --loaduserprofile causes the User Profile to be loaded into the
  NUnit Agent process.

See the release notes for a complete list of changes.

3.2.1

This is mainly a bugfix release, but it contains several features that were intended for the 3.4 release.

NUnit 3.2 introduced a change that ran each test on its own thread. In hindsight, this was a mistake and made it difficult for tests that required a specific context. We have reverted to the previous behaviour of running tests on the same thread unless a test attribute requires a new thread. We also added a new [SingleThreaded] attribute that you can apply to your test fixture to explicitly declare the requirement. Using this attribute allows the framework to raise an error if you mistakenly use an attribute on a test that requires a new thread.

Developers who target .NET 3.5 using the .NET 2.0 version of the framework ran into conflicts with some of the compatibility classes in NUnit. To fix this, we have reinstated the .NET 3.5 version of NUnit.

Very large test suites were using a large amount of memory causing paging and slow test runs on some systems. To reduce memory pressure, we are now releasing objects earlier, greatly reducing memory requirements.

The NUnit Engine now has an EventListener extension point for people who want to write extensions that respond to specific events during test runs.

For a full list of issues fixed in this release, please see the release notes.

3.2

In addition to numerous bug fixes, this release adds the long requested OrderAttribute, a new Assert.ThrowsAsync, Assert.That(0, Is.Zero) and other enhancements.

For a full list of issues fixed in this release, please see the release notes.

3.0.1

This release fixes critical issues reported against the initial 3.0 release, mainly around compatibility producing the NUnit 2 XML output format and async support for Windows 10. For a full list of issues fixed in this release, please see the release notes.

3.0

This is the final release of NUnit 3.0. See the release notes for details of all its features.

3.0.0-rc-3

This release fixes some errors in RC2 and is expected to be the final RC.

3.0.0-rc-2

This is the second release candidate for NUnit 3.0 which fixes a few issues that were found in the initial release. All the features we intend to include are present and this is the final step before releasing. If we have to make changes due to errors there will be additional release candidates. Otherwise, this build will be re-packaged as the final release.

For details of changes in this release, see the release notes.

3.0.0-rc

This is the initial release candidate for NUnit 3.0. All the features we intend to include are present and this is the final step before releasing. If we have to make changes due to errors there will be additional release candidates. Otherwise, this build will be re-packaged as the final release.

For details of changes in this release, see the release notes at https://github.com/nunit/docs/wiki/Release-Notes

3.0.0-beta-5

This is the fifth beta release of NUnit 3.0. We had a number of new features added and decided to have an additional beta before the final release.

For changes to the beta-5 release as well as cumulative changes see the release notes at https://github.com/nunit/docs/wiki/Release-Notes

3.0.0-beta-4

This is the fourth beta release of NUnit 3.0. We hope this will be the last beta before the final release, but will make the decision after reviewing the outstanding issues.

For changes to the beta-4 release as well as cumulative changes see the release notes at https://github.com/nunit/nunit/wiki/Release-Notes

3.0.0-beta-3

This is the third beta release of NUnit 3.0. We are planning one more beta next month before the final release.

This release changes the Engine API, so if you have a previous 3.0 release installed, you must uninstall it before installing this release.

For changes to the beta-3 release as well as cumulative changes see the release notes at https://github.com/nunit/nunit/wiki/Release-Notes

3.0.0-beta-2

This is the second beta release of NUnit 3.0 bringing us one step closer to the final release. This release splits the distribution of the Compact Framework version of the NUnit Framework out of the main package and adds a new core engine for use by devices and similar situations where reduced functionality is compensated for by reduced size and simplicity of usage.

For changes to the beta-2 release as well as cumulative changes see the release notes at https://github.com/nunit/nunit/wiki/Release-Notes

3.0.0-beta-1

This is the first beta release of NUnit 3.0.

For changes to the beta-2 release as well as cumulative changes see the release notes at https://github.com/nunit/nunit/wiki/Release-Notes

3.0.0-alpha-5

This is the fifth (and probably last) Alpha release of NUnit 3.0. It adds some important features, including implementation of addins in the test engine and provision of Windows installers for the framework and console runner.

3.0.0-alpha-4

This latest Alpha release of NUnit 3.0 adds several new features, including a driver that allows the 3.0 Test Engine to run tests created under NUnit 2.x and support for both NUnit and Visual Studio project formats.

3.0.0-alpha-3

This is the third alpha release of NUnit 3.0. See the Release Notes on the website or the CHANGES.txt document in the source folder for details.

3.0.0-alpha-2

This is the second alpha release of NUnit 3.0, fixing a number of bugs and limitations in the first alpha. See the Release Notes on the website or the CHANGES.txt document in the source folder for details.

3.0.0-alpha

This is the first true release of NUnit 3.0, after many months of pre-releases in the 2.9.x series.

It's still and alpha-level release, so we don't recommend it for production work. On the other hand, it's suitable for selective use on individual projects.

Currently, documentation is lacking but it's being developed. What is available may be seen at http://nunit.org

2.9.7

This is the final pre-alpha release of NUnit 3.0.

NOTE: The CHANGES.txt file included with the release is incorrect and does not include the latest changes. Download the separate CHANGES.txt file for a list of changes in this release.

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)