Migrate src/components/MemberRequestCard/MemberRequestCard.test.tsx from Jest to Vitest

[mandeepnh5]

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

Issue Number:
Fixes #2830

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

Summary by CodeRabbit

• Tests
  • Updated the MemberRequestCard component tests to use the Vitest framework.
  • Replaced jest mocking functions with vi for improved testing consistency.
  • Adjusted import statements to incorporate Vitest's describe and expect functions.

[coderabbitai]

Walkthrough

This pull request focuses on migrating the MemberRequestCard component's test file from Jest to Vitest. The change involves updating the testing framework imports and mocking functions to align with Vitest's syntax. The test file has been renamed from .test.tsx to .spec.tsx, which is a common convention when transitioning to Vitest. The core test logic remains unchanged, ensuring that the component's behavior is still thoroughly validated.

Changes

File	Change Summary
src/components/MemberRequestCard/MemberRequestCard.spec.tsx	Replaced Jest imports with Vitest imports (describe, vi, expect), updated global mock for alert()

Assessment against linked issues

Objective	Addressed	Explanation
Replace Jest-specific functions with Vitest equivalents [#2830]	✅
Rename test file from .test.* to .spec.* [#2830]	✅
Ensure tests pass using npm run test:vitest [#2830]	❓	Requires actual test run verification
Maintain 100% test coverage [#2830]	❓	Requires coverage report verification

Possibly related issues

• Refactor : src/components/AgendaItems/AgendaItemsPreviewModal.test.tsx from Jest to Vitest #2490: Refactoring AgendaItemsPreviewModal tests from Jest to Vitest
• Refactor : src/components/AgendaItems/AgendaItemsUpdateModal.test.tsx from Jest to Vitest #2491: Refactoring AgendaItemsUpdateModal tests from Jest to Vitest
• Refactor: src/components/AddOn/support/components/MainContent/MainContent.test.tsx from Jest to Vitest #2475: Refactoring MainContent tests from Jest to Vitest

Possibly related PRs

• Refactor Tests: Migrate src/screens/UserPortal/UserScreen/UserScreen.tsx from Jest to Vitest #2632: Migration of UserScreen component 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: Migration of MemberDetailScreen tests to Vitest

Suggested reviewers

• palisadoes

Poem

🐰 A testing tale of migration's might,
From Jest to Vitest, we take flight!
Mocks and describes, now freshly dressed,
Our code stands strong, thoroughly assessed! 🧪
Hop, hop, hooray for framework's new delight! 🚀

---

📜 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 1eab2c1 and db8c511.

📒 Files selected for processing (1)

• src/components/MemberRequestCard/MemberRequestCard.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 (2)

src/components/MemberRequestCard/MemberRequestCard.spec.tsx (2)

14-14: Successful Migration of Test Imports

Importing describe, vi, and expect from Vitest is correct for replacing Jest functionalities. This aligns well with the PR goal of migrating to Vitest.

---

69-69: Valid Global Alert Mock

Assigning global.alert to vi.fn() is an appropriate way to mock alert in Vitest. No issues found with its usage or scope.

---

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.

[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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.82%. Comparing base (1eab2c1) to head (db8c511).
Report is 2 commits behind head on develop-postgres.

Additional details and impacted files

@@                  Coverage Diff                  @@
##           develop-postgres    #2859       +/-   ##
=====================================================
+ Coverage             64.63%   87.82%   +23.18%     
=====================================================
  Files                   296      313       +17     
  Lines                  7369     8222      +853     
  Branches               1609     1854      +245     
=====================================================
+ Hits                   4763     7221     +2458     
+ Misses                 2371      802     -1569     
+ Partials                235      199       -36     

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