search

GHPReporter / Ghpr.NUnit

Adapter for NUnit 3 (generate HTML report for NUnit 3)
http://ghpreporter.github.io/
MIT License
35 stars 14 forks source link

Bump NUnit from 3.12.0 to 3.13.1 in /Ghpr.NUnit #95

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[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 - 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
  • 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) - `@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) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)
dependabot-preview[bot] commented 3 years ago

Superseded by #99.