Migrated src/components/RecurrenceOptions/* from Jest to Vitest.

[mandeepnh5]

What kind of change does this PR introduce?
This PR will migrate the src/components/RecurrenceOptions/* from Jest to Vitest.

Issue Number:
Fixes #2807

Did you add tests for your changes?
Yes

Snapshots/Videos:

If relevant, did you update the documentation?
No

Does this PR introduce a breaking change?
No

Have you read the contributing guide?
Yes

Summary by CodeRabbit

• Tests
  • Transitioned testing framework from Jest to Vitest in CustomRecurrence.spec.tsx and RecurrenceOptions.spec.tsx.
  • Updated mock implementations for @mui/x-date-pickers/DateTimePicker and react-toastify.

[github-actions]

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

[coderabbitai]

Walkthrough

This pull request focuses on migrating test files for the RecurrenceOptions components from Jest to Vitest. Specifically, the changes involve updating two test files: CustomRecurrence.spec.tsx and RecurrenceOptions.spec.tsx. The migration includes replacing Jest-specific mocking and testing functions with their Vitest equivalents, updating import statements, and ensuring compatibility with the Vitest testing framework.

Changes

File	Change Summary
src/components/RecurrenceOptions/CustomRecurrence.spec.tsx	- Added Vitest imports - Replaced jest.mock with vi.mock - Updated mock function declarations from jest.fn() to vi.fn()
src/components/RecurrenceOptions/RecurrenceOptions.spec.tsx	- Added Vitest imports - Replaced jest.mock with vi.mock - Updated mock function declarations

Assessment against linked issues

Objective	Addressed	Explanation
Refactor from Jest to Vitest [#2807]	✅
Replace Jest-specific functions with Vitest equivalents [#2807]	✅
Rename test files to .spec.* suffix [#2807]	✅
Ensure tests pass with npm run test:vitest [#2807]	❓	Requires actual test run verification

Possibly related issues

• Refactor: src/screens/EventManagement from Jest to Vitest #2546: Refactoring src/screens/EventManagement from Jest to Vitest, similar migration approach
• Refactor: src/screens/UserPortal/Volunteer/Invitations from Jest to Vitest #2583: Migrating src/screens/UserPortal/Volunteer/Invitations tests to Vitest
• Refactor : src/components/CheckIn/CheckInModal.test.tsx from Jest to Vitest #2494: Refactoring CheckInModal.test.tsx from Jest to Vitest

Possibly related PRs

• Refactor: src/screens/UserPortal/Volunteer/UpcomingEvents from Jest to Vitest #2623: Migration of UpcomingEvents tests to Vitest
• Refactor:src/screens/UserPortal/Events from Jest to Vitest  #2639: Transition of Events component tests to Vitest
• refactor:vitest to MemberDetailScreen #2662: Update of MemberDetail tests to Vitest
• Refactor:Vitest to OrgPeople Screen #2663: Migration of OrganizationPeople tests to Vitest

Suggested reviewers

• palisadoes

Poem

🐰 Hopping through code with glee,
Jest to Vitest, a testing spree!
Mocks and functions, now reborn,
A testing framework freshly sworn.
Refactoring with rabbit might! 🧪

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 35cce16 and d30d12f.

📒 Files selected for processing (2)

• src/components/RecurrenceOptions/CustomRecurrence.spec.tsx (2 hunks)
• src/components/RecurrenceOptions/RecurrenceOptions.spec.tsx (2 hunks)

🧰 Additional context used

📓 Learnings (1)

📓 Common learnings

Learnt from: bitbard3
PR: PalisadoesFoundation/talawa-admin#2588
File: src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx:145-155
Timestamp: 2024-12-02T04:20:11.745Z
Learning: In PRs focused solely on refactoring test cases from Jest to Vitest, avoid suggesting optimizations or changes outside the migration scope.

🔇 Additional comments (6)

src/components/RecurrenceOptions/RecurrenceOptions.spec.tsx (3)

25-25: Correct import for Vitest.

Good job swapping out the Jest imports for Vitest. This change is aligned with your migration objective.

---

55-60: Mock transition from Jest to Vitest is handled properly.

Replacing jest.mock with vi.mock and utilizing vi.importActual ensures consistency with Vitest’s API.

---

64-68: Uninterrupted mock usage upgrade.

These updates cleanly replace jest.fn with vi.fn for the toast object, maintaining the same behavior under Vitest.

src/components/RecurrenceOptions/CustomRecurrence.spec.tsx (3)

25-25: Consistent Vitest import.

Similar to the other file, switching to Vitest imports is correct for the new test framework.

---

51-56: Robust mocking approach with Vitest.

Importing the actual DateTimePicker and aliasing it works seamlessly under Vitest. Good usage of vi.importActual.

---

60-64: Smooth migration of toast mocks.

Adopting vi.mock and vi.fn ensures no behavioral changes while switching frameworks.

---

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>, 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.

[mandeepnh5]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.99%. Comparing base (35cce16) to head (d30d12f).
Report is 3 commits behind head on develop-postgres.

Additional details and impacted files

@@                  Coverage Diff                  @@
##           develop-postgres    #2911       +/-   ##
=====================================================
+ Coverage             58.52%   87.99%   +29.47%     
=====================================================
  Files                   299      316       +17     
  Lines                  7414     8265      +851     
  Branches               1621     1866      +245     
=====================================================
+ Hits                   4339     7273     +2934     
+ Misses                 2828      779     -2049     
+ Partials                247      213       -34     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mandeepnh5]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.