Refactor src/components/UpdateSession/UpdateSession.test.tsx from Jest to Vitest

[abbi4code]

What kind of change does this PR introduce?
This PR migrates the test cases in src/components/UpdateSession/UpdateSession.test.tsx from Jest to Vitest, ensuring compatibility with Vitest .

✅ Replace Jest-specific functions and mocks with Vitest equivalents
✅ Ensure all tests in src/components/UpdateSession/UpdateSession.test.tsx from Jest to Vitest.pass after migration using npm run test:vitest
✅ Maintain the test coverage for the file as 100% after migration
✅ Upload a video or photo for this specific file coverage is 100% in the PR description

Issue Number:

Fixes #2823

Did you add tests for your changes?
yes

Snapshots/Videos:

Summary by CodeRabbit

• Tests
  • Updated testing framework from Jest to Vitest for the UpdateSession component.
  • Adjusted mocking and spy methods to align with Vitest's API.
  • Maintained existing test logic while ensuring compatibility with the new framework.

[coderabbitai]

Walkthrough

This pull request focuses on refactoring the UpdateSession.spec.tsx test file from Jest to Vitest. The changes involve updating the testing framework-specific syntax, including mocking methods, spy methods, and test function declarations. The core test logic and structure remain unchanged, ensuring that the component's behavior is still thoroughly tested with the new testing framework.

Changes

File	Change Summary
src/components/UpdateSession/UpdateSession.spec.tsx	- Replaced Jest mocking methods with Vitest equivalents - Updated spy methods from Jest to Vitest - Renamed test functions from test to it - Maintained original test coverage and logic

Assessment against linked issues

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

Possibly related issues

• Refactor : src/components/AgendaItems/AgendaItemsUpdateModal.test.tsx from Jest to Vitest #2491: Similar Vitest migration for AgendaItemsUpdateModal.test.tsx
• Refactor: src/components/AddOn/support/components/MainContent/MainContent.test.tsx from Jest to Vitest #2475: Vitest migration for MainContent.test.tsx
• Refactor : src/components/CheckIn/TableRow.test.tsx from Jest to Vitest #2496: Vitest migration for CheckIn/TableRow.test.tsx

Possibly related PRs

• Refactor: src/screens/UserPortal/Volunteer/UpcomingEvents from Jest to Vitest #2623: Migrating UpcomingEvents component tests to Vitest
• Refactor Tests: Migrate src/screens/UserPortal/UserScreen/UserScreen.tsx from Jest to Vitest #2632: Transitioning UserScreen component tests to Vitest
• Refactor:src/screens/UserPortal/Events from Jest to Vitest  #2639: Migrating Events component tests to Vitest

Suggested reviewers

• palisadoes

Poem

🐰 Hopping from Jest to Vitest's land,
Test files dancing to a new command!
Mocks and spies, now freshly reborn,
Code coverage still perfectly worn.
A testing rabbit's joyful refrain! 🧪

---

📜 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 471f113 and 9739d26.

📒 Files selected for processing (1)

• src/components/UpdateSession/UpdateSession.spec.tsx (11 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 (16)

src/components/UpdateSession/UpdateSession.spec.tsx (16)

3-3: Well-imported testing-library utilities.
This import statement properly brings in the required utilities (render, screen, act, within) from React Testing Library. There are no Jest-specific references here, so nothing further is needed for the Vitest migration.

---

13-13: Correct import for Vitest.
Importing vi from vitest is the right approach to replace Jest's globals.

---

15-15: Informative documentation comment.
The file-level comment accurately describes what the tests cover. Good job keeping it clear.

---

72-76: Migration from jest.mock to vi.mock.
The mocking of react-toastify has been successfully updated from Jest to Vitest. This ensures the toast methods work within Vitest's mocking infrastructure.

---

80-81: Mocking errorHandler with vi.mock.
This swap from jest.mock to vi.mock is correct. All references to errorHandler will now be intercepted by Vitest.

---

86-86: Using vi.spyOn(console, 'warn').
Replacing Jest’s spyOn with Vitest’s vi.spyOn is consistent and correct for intercepting console warnings.

---

90-90: Using vi.clearAllMocks() for cleanup.
This change from jest.clearAllMocks() to vi.clearAllMocks() aligns perfectly with Vitest’s API.

---

93-94: Replacing jest.fn() with vi.fn().
Vitest’s vi.fn() is used correctly for creating mock functions. The test logic remains intact.

---

113-114: Consistent usage of vi.fn().
Again, replacing jest.fn() with vi.fn() ensures test cohesion under Vitest.

---

133-134: Maintaining test logic.
Confirming that vi.fn() is used for mocking. No additional changes or refactors needed here.

---

154-155: Valid approach for slider interaction test.
The code uses vi.fn() for the callback, preserving the same test approach while moving off Jest.

---

173-173: No Jest references in the test block.
This test block remains intact and does not require further changes aside from the broader migration.

---

207-207: Still aligned with Vitest.
The test logic to verify session updates remains the same, and references are properly updated to Vi if any existed.

---

232-232: Handling query errors still tested under Vitest.
The test scenario and error mocking logic transfer seamlessly to Vitest.

---

257-257: Confirmed error flow with Vitest.
The test coverage for API error handling remains consistent post-migration.

---

310-310: Null community object test.
This test continues to work with Vitest, ensuring the new test framework can handle all states.

---

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.84%. Comparing base (471f113) to head (9739d26).
Report is 3 commits behind head on develop-postgres.

Additional details and impacted files

@@                  Coverage Diff                  @@
##           develop-postgres    #2863       +/-   ##
=====================================================
+ Coverage             63.58%   87.84%   +24.25%     
=====================================================
  Files                   296      313       +17     
  Lines                  7371     8224      +853     
  Branches               1610     1799      +189     
=====================================================
+ Hits                   4687     7224     +2537     
+ Misses                 2451      801     -1650     
+ Partials                233      199       -34     

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

[palisadoes]

1. Are you using a plugin for your comments?
2. It would be good to apply it to all our code