Upgrade testing library jest dom

[VanshikaSabharwal]

What kind of change does this PR introduce?

bugfix, security, dependencies

Issue Number:

Fixes #1951

Did you add tests for your changes?

No

Snapshots/Videos:

Summary

The motivation for this change is to upgrade the @testing-library/jest-dom package from version 5.16.5 to 6.4.2. This upgrade addresses potential issues with outdated dependencies, improves compatibility with the latest versions of other tools, and ensures that the testing environment remains up to date. By upgrading, the project will benefit from new features, bug fixes, and improved performance offered by the newer version of the package.

Issue

Other information

Have you read the contributing guide?

Yes

Summary by CodeRabbit

Summary by CodeRabbit

• Chores
  • Updated the @testing-library/jest-dom package to a newer version, enhancing testing capabilities and ensuring compatibility with the latest best practices.

[coderabbitai]

Walkthrough

The primary change involves updating the @testing-library/jest-dom package from version 5.14.1 to 6.4.2 in the devDependencies section of the package.json file. This major version upgrade is intended to incorporate new features, enhancements, and bug fixes from the library, potentially requiring adjustments in the codebase to ensure compatibility with the updated syntax and methods.

Changes

Files	Change Summary
package.json	Updated @testing-library/jest-dom version from ^5.14.1 to ^6.4.2.

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade @testing-library/jest-dom to 6.4.2 (1951)	✅
All tests must be valid and pass (1951)	❓	Test outcomes are not verified in this PR.
Upgrade @testing-library/jest-dom to 6.4.5 (2015)	❌	The version upgraded is 6.4.2, not 6.4.5.
Existing configurations must not be modified (1951)	✅
No other functionality must be affected (1951)	❓	Impact on existing functionality is unclear.

Possibly related issues

• Upgrade package @testing-library/jest-dom from 5.16.5 to 6.4.5 #2015: This issue seeks to upgrade @testing-library/jest-dom to 6.4.5, which the current PR partially addresses by upgrading to 6.4.2, indicating that a further upgrade may be needed.

🐇 In the garden I hop and play,
With jest-dom brightening my day.
A version change, oh what a thrill,
New features and fixes, a joyous spill!
Let tests run free, let them all pass,
In the meadow of code, we’ll make our mark last! 🌼✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.

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.

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 968c284 and 2e83f68.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (1)

• package.json (1 hunks)

Additional comments not posted (1)

package.json (1)

99-99: Verify compatibility with @testing-library/jest-dom version 6.4.2.

This major version upgrade may introduce breaking changes or require updates in the codebase. Ensure that all tests pass successfully and that the codebase is compatible with the new version.

Run the following script to verify the test results: