Flow.Launcher icon indicating copy to clipboard operation
Flow.Launcher copied to clipboard

Published 20 hours ago • verified publisher icon Flow-Launcher

Bump nunit from 3.14.0 to 4.2.1

Open dependabot[bot] opened this issue 1 year ago • 4 comments
trafficstars

Bumps nunit from 3.14.0 to 4.2.1.

Release notes

Sourced from nunit's releases.

NUnit 4.2.1

Hotfix release for Issue #4794 and #4795, affecting .Net Framework.

NUnit 4.2.0

See release notes

NUnit 4.1.0

See release notes

NUnit 4.0.1

Patch release to fix windows targets

See release notes and See migration guide

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.

For further changes, see release notes

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"

... (truncated)

Commits

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

dependabot[bot] avatar Aug 26 '24 22:08 dependabot[bot]

Walkthrough

Walkthrough

The project file Flow.Launcher.Test.csproj has been updated to reference a newer version of the NUnit testing framework, changing from version 3.14.0 to 4.2.1. This update reflects a shift to a more recent version of the package, which may include various enhancements and fixes relevant to the testing environment.

Changes

Files Change Summary
Flow.Launcher.Test/Flow.Launcher.Test.csproj Updated NUnit package reference from version 3.14.0 to 4.2.1.

Poem

In the meadow where bunnies play,
A new NUnit version brightens the day!
Hops and skips, we test with glee,
Bugs are squashed, as happy as can be!
With every change, our code will thrive,
A joyful leap, our tests come alive! 🐰✨

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

coderabbitai[bot] avatar Aug 26 '24 22:08 coderabbitai[bot]

@check-spelling-bot Report

:red_circle: Please review

See the :open_file_folder: files view, the :scroll:action log, or :memo: job summary for details.

:x: Errors Count
:x: ignored-expect-variant 1
:warning: non-alpha-in-dictionary 13

See :x: Event descriptions for more information.

If the flagged items are :exploding_head: false positives

If items relate to a ...

  • binary file (or some other file you wouldn't want to check at all).

    Please add a file path to the excludes.txt file matching the containing file.

    File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

    ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

  • well-formed pattern.

    If you can write a pattern that would match it, try adding it to the patterns.txt file.

    Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

    Note that patterns can't match multiline strings.

github-actions[bot] avatar Aug 26 '24 22:08 github-actions[bot]

🥷 Code experts: jjw24

jjw24 has most 🧠 knowledge in the files.

See details

Flow.Launcher.Test/Flow.Launcher.Test.csproj

Knowledge based on git-blame: jjw24: 22%

To learn more about /:\ gitStream - Visit our Docs

gitstream-cm[bot] avatar Aug 26 '24 22:08 gitstream-cm[bot]

Be a legend :trophy: by adding a before and after screenshot of the changes you made, especially if they are around UI/UX.

gitstream-cm[bot] avatar Aug 26 '24 22:08 gitstream-cm[bot]

Superseded by #2951.

dependabot[bot] avatar Sep 02 '24 22:09 dependabot[bot]