[Snyk] Upgrade @testing-library/jest-dom from 5.12.0 to 5.17.0

[nejidevelops]

Snyk has created this PR to upgrade @testing-library/jest-dom from 5.12.0 to 5.17.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 12 versions ahead of your current version.

• The recommended version was released 2 years ago.

Release notes

Package name: @testing-library/jest-dom

• 5.17.0 - 2023-07-18
  

  5.17.0 (2023-07-18)

  Features

  • New toHaveAccessibleErrorMessage better implementing the spec, deprecate toHaveErrorMessage (#503) (d717c66)
• 5.16.5 - 2022-08-04
  

  5.16.5 (2022-08-04)

  Bug Fixes

  • migrate ccs v3 to @ adobe/css-tools v4 (#470) (948d90f)
• 5.16.4 - 2022-04-05
  

  5.16.4 (2022-04-05)

  Bug Fixes

  • Support unenclosed inner text for details elements in to be visible (#396) (af18453)
• 5.16.3 - 2022-03-24
  

  5.16.3 (2022-03-24)

  Bug Fixes

  • clarify toHaveFocus message when using .not (#447) (6988a67)
• 5.16.2 - 2022-02-03
  

  5.16.2 (2022-02-03)

  Bug Fixes

  • add custom element support to toBeDisabled (#368) (8162115)
• 5.16.1 - 2021-12-06
  

  5.16.1 (2021-12-06)

  Bug Fixes

  • Improve toHaveClass error message format (#405) (a9beb47)
• 5.16.0 - 2021-12-03
  

  5.16.0 (2021-12-03)

  Features

  • Update aria-query to 5.0.0 (#414) (de26c7a)
• 5.15.1 - 2021-11-23
  

  5.15.1 (2021-11-23)

  Bug Fixes

  • wrong deprecate error message (#422) (dfcefa2)
• 5.15.0 - 2021-11-02
  

  5.15.0 (2021-11-02)

  Features

  • import parse directly from css (#415) (4cb606c)
• 5.14.1 - 2021-06-11
  

  5.14.1 (2021-06-11)

  Bug Fixes

  • Updates deprecated matchers info (#378) (fc9ce6d)
• 5.14.0 - 2021-06-11
• 5.13.0 - 2021-06-03
• 5.12.0 - 2021-04-22

from @testing-library/jest-dom GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gemini-code-assist]

Summary of Changes

Hello @nejidevelops, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on maintaining the project's dependencies by updating a key testing library. The primary goal is to ensure the project benefits from the latest features, bug fixes, and security improvements provided by the updated package, thereby enhancing the overall stability and maintainability of the codebase.

Highlights

• Dependency Upgrade: This pull request, automatically generated by Snyk, upgrades the @testing-library/jest-dom package from version 5.12.0 to 5.17.0.
• New Feature and Deprecation: Version 5.17.0 introduces a new matcher toHaveAccessibleErrorMessage and deprecates the older toHaveErrorMessage.
• Maintenance and Security: The upgrade aims to keep dependencies up-to-date, facilitating easier fixes for existing vulnerabilities and quicker identification of new ones.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request upgrades @testing-library/jest-dom to version 5.17.0. This is a significant update that includes a potentially breaking change: the toHaveErrorMessage matcher has been deprecated and replaced with toHaveAccessibleErrorMessage. It is important to update any tests that use the deprecated matcher. I also recommend running the full test suite to ensure there are no regressions. Furthermore, this pull request should include the updated package-lock.json file to ensure that builds are reproducible across all environments.

[gemini-code-assist]

The toHaveErrorMessage matcher is deprecated in @testing-library/jest-dom v5.17.0 and has been replaced by toHaveAccessibleErrorMessage. You should update any tests using the old matcher to prevent future breakages and ensure your tests align with the library's latest API. Running the full test suite after this upgrade is also crucial to catch any potential regressions.