DotNetAnalyzers / ReflectionAnalyzers

Analyzers checking System.Reflection
MIT License
80 stars 8 forks source link

Bump NUnit from 3.12.0 to 3.13.1 #236

Closed dependabot[bot] closed 3 years ago

dependabot[bot] commented 3 years ago

Bumps NUnit from 3.12.0 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

Changelog

Sourced from NUnit's changelog.

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

... (truncated)

Commits
  • 248dae7 Merge pull request #3748 from nunit/issue/3745
  • 41021cc Use sourcelink for linking the PDB files
  • b60b1fd Checkpointing enabling sourcelink
  • 47f787f Add assemblies to the snupkg even though they aren't added
  • 8a829ed Updates based on code review
  • 009c228 Upload snupkg to AppVeyor
  • 35aefae - Partially reverts #3464
  • c7afecb Merge pull request #3744 from gleb-osokin/master
  • 6a7fc74 Merge pull request #3741 from nunit/Poimen-issue-2339
  • 787f6db Updates base on code review
  • Additional commits viewable in compare view


Dependabot compatibility score

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)