Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixed:#2072 Upgraded package @testing-library/user-event from 12.8.3 to 14.5.2 #3122

Open
wants to merge 2 commits into
base: develop-postgres
Choose a base branch
from

Conversation

gurramkarthiknetha
Copy link
Contributor

@gurramkarthiknetha gurramkarthiknetha commented Jan 2, 2025

What kind of change does this PR introduce?

This PR upgrades the @testing-library/user-event package from version 12.8.3 to 14.5.2 to resolve dependency issues, align with the latest features, and improve stability.

Issue Number:

Fixes #2072

Did you add tests for your changes?

Yes, existing tests were updated to comply with the new syntax and methods introduced in the upgraded version. Additional tests were added where necessary.

Snapshots/Videos:

Not applicable as this change primarily involves a dependency upgrade and test adjustments.

If relevant, did you update the documentation?

No updates were necessary for documentation as this is a dependency change that does not impact external documentation.

Summary

Upgraded @testing-library/user-event to 14.5.2.
Updated test cases to reflect new syntax and features.
Verified all tests pass to ensure compatibility.
Removed any redundant imports and resolved circular dependencies as per the release notes.

Does this PR introduce a breaking change?

No, this change does not introduce breaking changes to the application itself. It updates internal testing dependencies, ensuring they function correctly.

Other information

Release notes for 14.5.2 indicate resolved bugs, added named exports, and type improvements that enhance compatibility and developer experience.

Have you read the contributing guide?

Yes, I have reviewed and followed the contributing guidelines.

Summary by CodeRabbit

Based on the comprehensive summary, here are the release notes:

  • Dependencies

    • Updated @testing-library/user-event from ^12.1.10 to ^14.5.2
    • Added @testing-library/dom at version ^10.4.0
    • Downgraded jest-preview from ^0.3.1 to ^0.2.3
  • Testing Improvements

    • Migrated userEvent imports from default to named imports across all test files
    • Enhanced asynchronous handling of user interactions by adding await to userEvent method calls
    • Improved test reliability by ensuring user events are properly awaited before assertions

These changes primarily focus on updating testing libraries and improving the robustness of test suites by ensuring proper handling of asynchronous user interactions.

Copy link
Contributor

coderabbitai bot commented Jan 2, 2025

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

📥 Commits

Reviewing files that changed from the base of the PR and between b60c476 and 32566de.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (82)
  • package.json (2 hunks)
  • src/components/AddOn/core/AddOnEntry/AddOnEntry.spec.tsx (1 hunks)
  • src/components/AddOn/core/AddOnRegister/AddOnRegister.spec.tsx (4 hunks)
  • src/components/AddOn/core/AddOnStore/AddOnStore.spec.tsx (3 hunks)
  • src/components/AddPeopleToTag/AddPeopleToTag.test.tsx (4 hunks)
  • src/components/Advertisements/Advertisements.spec.tsx (4 hunks)
  • src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.spec.tsx (3 hunks)
  • src/components/AgendaCategory/AgendaCategoryContainer.spec.tsx (12 hunks)
  • src/components/AgendaItems/AgendaItemsContainer.spec.tsx (12 hunks)
  • src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx (3 hunks)
  • src/components/DynamicDropDown/DynamicDropDown.spec.tsx (4 hunks)
  • src/components/EditCustomFieldDropDown/EditCustomFieldDropDown.spec.tsx (1 hunks)
  • src/components/EventListCard/EventListCard.spec.tsx (39 hunks)
  • src/components/EventManagement/EventAgendaItems/EventAgendaItems.spec.tsx (3 hunks)
  • src/components/EventManagement/EventAttendance/EventAttendance.spec.tsx (4 hunks)
  • src/components/EventManagement/EventAttendance/EventStatistics.spec.tsx (1 hunks)
  • src/components/EventRegistrantsModal/AddOnSpotAttendee.spec.tsx (4 hunks)
  • src/components/LeftDrawer/LeftDrawer.test.tsx (3 hunks)
  • src/components/LeftDrawerOrg/LeftDrawerOrg.spec.tsx (3 hunks)
  • src/components/MemberRequestCard/MemberRequestCard.spec.tsx (3 hunks)
  • src/components/OrgAdminListCard/OrgAdminListCard.spec.tsx (2 hunks)
  • src/components/OrgListCard/OrgListCard.spec.tsx (1 hunks)
  • src/components/OrgPeopleListCard/OrgPeopleListCard.spec.tsx (1 hunks)
  • src/components/OrgPostCard/OrgPostCard.spec.tsx (24 hunks)
  • src/components/OrgSettings/ActionItemCategories/CategoryModal.spec.tsx (4 hunks)
  • src/components/OrgSettings/ActionItemCategories/OrgActionItemCategories.spec.tsx (6 hunks)
  • src/components/OrgSettings/AgendaItemCategories/AgendaCategoryUpdateModal.spec.tsx (1 hunks)
  • src/components/OrgSettings/AgendaItemCategories/OrganizationAgendaCategory.spec.tsx (8 hunks)
  • src/components/OrgSettings/General/OrgProfileFieldSettings/OrgProfileFieldSettings.spec.tsx (6 hunks)
  • src/components/OrgSettings/General/OrgUpdate/OrgUpdate.spec.tsx (3 hunks)
  • src/components/Pagination/Pagination.spec.tsx (3 hunks)
  • src/components/ProfileDropdown/ProfileDropdown.spec.tsx (7 hunks)
  • src/components/RecurrenceOptions/CustomRecurrence.spec.tsx (19 hunks)
  • src/components/RecurrenceOptions/RecurrenceOptions.spec.tsx (14 hunks)
  • src/components/RequestsTableItem/RequestsTableItem.spec.tsx (5 hunks)
  • src/components/TagActions/TagActions.test.tsx (9 hunks)
  • src/components/UpdateSession/UpdateSession.spec.tsx (7 hunks)
  • src/components/UserListCard/UserListCard.spec.tsx (3 hunks)
  • src/components/UserPasswordUpdate/UserPasswordUpdate.spec.tsx (6 hunks)
  • src/components/UserPortal/CommentCard/CommentCard.spec.tsx (11 hunks)
  • src/components/UserPortal/ContactCard/ContactCard.spec.tsx (3 hunks)
  • src/components/UserPortal/EventCard/EventCard.spec.tsx (2 hunks)
  • src/components/UserPortal/OrganizationNavbar/OrganizationNavbar.spec.tsx (7 hunks)
  • src/components/UserPortal/PostCard/PostCard.spec.tsx (10 hunks)
  • src/components/UserPortal/Register/Register.spec.tsx (8 hunks)
  • src/components/UserPortal/StartPostModal/StartPostModal.spec.tsx (6 hunks)
  • src/components/UserPortal/UserNavbar/UserNavbar.spec.tsx (9 hunks)
  • src/components/UserPortal/UserSidebarOrg/UserSidebarOrg.spec.tsx (3 hunks)
  • src/components/UsersTableItem/UserTableItem.spec.tsx (2 hunks)
  • src/components/Venues/VenueModal.spec.tsx (3 hunks)
  • src/screens/BlockUser/BlockUser.spec.tsx (7 hunks)
  • src/screens/CommunityProfile/CommunityProfile.spec.tsx (4 hunks)
  • src/screens/EventManagement/EventManagement.test.tsx (3 hunks)
  • src/screens/EventVolunteers/Requests/Requests.spec.tsx (5 hunks)
  • src/screens/EventVolunteers/VolunteerContainer.spec.tsx (2 hunks)
  • src/screens/EventVolunteers/VolunteerGroups/VolunteerGroupDeleteModal.spec.tsx (4 hunks)
  • src/screens/EventVolunteers/VolunteerGroups/VolunteerGroupModal.spec.tsx (7 hunks)
  • src/screens/EventVolunteers/VolunteerGroups/VolunteerGroups.spec.tsx (4 hunks)
  • src/screens/EventVolunteers/Volunteers/VolunteerCreateModal.spec.tsx (3 hunks)
  • src/screens/EventVolunteers/Volunteers/VolunteerDeleteModal.spec.tsx (4 hunks)
  • src/screens/EventVolunteers/Volunteers/Volunteers.spec.tsx (5 hunks)
  • src/screens/ForgotPassword/ForgotPassword.spec.tsx (9 hunks)
  • src/screens/FundCampaignPledge/FundCampaignPledge.test.tsx (7 hunks)
  • src/screens/Leaderboard/Leaderboard.spec.tsx (3 hunks)
  • src/screens/LoginPage/LoginPage.spec.tsx (20 hunks)
  • src/screens/ManageTag/ManageTag.spec.tsx (16 hunks)
  • src/screens/MemberDetail/MemberDetail.spec.tsx (7 hunks)
  • src/screens/OrgList/OrgList.test.tsx (10 hunks)
  • src/screens/OrgPost/OrgPost.test.tsx (14 hunks)
  • src/screens/OrgSettings/OrgSettings.spec.tsx (4 hunks)
  • src/screens/OrganizationActionItems/OrganizationActionItems.spec.tsx (8 hunks)
  • src/screens/OrganizationDashboard/OrganizationDashboard.spec.tsx (10 hunks)
  • src/screens/OrganizationEvents/OrganizationEvents.spec.tsx (11 hunks)
  • src/screens/OrganizationFundCampaign/OrganizationFundCampaign.test.tsx (3 hunks)
  • src/screens/OrganizationFunds/OrganizationFunds.spec.tsx (3 hunks)
  • src/screens/OrganizationPeople/OrganizationPeople.spec.tsx (22 hunks)
  • src/screens/OrganizationTags/OrganizationTags.spec.tsx (7 hunks)
  • src/screens/Requests/Requests.spec.tsx (3 hunks)
  • src/screens/SubTags/SubTags.spec.tsx (10 hunks)
  • src/screens/UserPortal/Campaigns/Campaigns.spec.tsx (7 hunks)
  • src/screens/UserPortal/Donate/Donate.spec.tsx (16 hunks)
  • src/screens/UserPortal/Events/Events.spec.tsx (8 hunks)
 _______________________________________________________
< Coding ain't done 'til all the Tests run. 'Nuff said. >
 -------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       /   づ

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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

Copy link

github-actions bot commented Jan 2, 2025

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

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

@duplixx
Copy link
Member

duplixx commented Jan 4, 2025

@gurramkarthiknetha please fix the conflicting file changes

@gurramkarthiknetha
Copy link
Contributor Author

@gurramkarthiknetha please fix the conflicting file changes

Okay , please review the pr #3012

Comment on lines 154 to +155
"jest-location-mock": "^2.0.0",
"jest-preview": "^0.3.1",
"jest-preview": "^0.2.3",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why downgraded this ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants