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.

Sign up for GitHub

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

Jump to bottom

Migrate to vitest #2947

Merged
merged 2 commits into from
Dec 26, 2024
Merged

Migrate to vitest #2947

merged 2 commits into from
Dec 26, 2024

Conversation

gracefullcoder
Copy link
Contributor

@gracefullcoder gracefullcoder commented Dec 26, 2024 •
edited by coderabbitai bot
Loading

What kind of change does this PR introduce?

Replace Jest-specific functions and mocks with Vitest equivalents in LeftDrawerOrg.test.tsx testing file

Issue Number:

Fixes #2833

Did you add tests for your changes?

Yes

Snapshots/Videos:

ML19

If relevant, did you update the documentation?

No

Summary

  • Sir Made changes as specified by you.
    -Made Changes as per the context provide also svg images are passed in test and all 9/9 test passed.
    -Migrated test for ChangeLanguageDropdown.tsx from jest to vitest.

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.
    • Updated mocking functions and cleanup methods to align with Vitest standards.
    • Maintained existing test structure and functionality for the LeftDrawerOrg component.

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 26, 2024 •
edited
Loading

Walkthrough

This pull request focuses on migrating the test file LeftDrawerOrg.spec.tsx from Jest to Vitest. The changes involve updating import statements, mocking functions, and cleanup methods to align with Vitest's syntax. The core test cases remain unchanged, ensuring that the component's behavior is validated using the new testing framework.

Changes

File Change Summary
src/components/LeftDrawerOrg/LeftDrawerOrg.spec.tsx - Replaced Jest imports with Vitest imports
- Updated mocking functions from jest.mock() to vi.mock()
- Replaced jest.fn() with vi.fn()
- Changed cleanup method from jest.clearAllMocks() to vi.clearAllMocks()

Assessment against linked issues

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

Possibly related issues

Possibly related PRs

Suggested reviewers

  • palisadoes

Poem

🐰 A Jest-to-Vitest tale, oh so neat!
Mocks transformed with a testing beat
Functions dance, imports realign
Code migration, simply divine
Rabbit hops through framework's gate 🧪

📜 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 6997a04 and 695f842.

📒 Files selected for processing (1)
  • src/components/LeftDrawerOrg/LeftDrawerOrg.spec.tsx (5 hunks)
🧰 Additional context used
📓 Learnings (2)
📓 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.
src/components/LeftDrawerOrg/LeftDrawerOrg.spec.tsx (1) 
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 (5)
src/components/LeftDrawerOrg/LeftDrawerOrg.spec.tsx (5)

1-1: Retaining @testing-library/jest-dom is acceptable within Vitest-based tests.
This import offers helpful DOM matchers and is compatible with Vitest when properly configured, so no changes are needed here.

18-18: Successful migration to Vitest imports.
Using vi, describe, test, and expect is consistent with Vitest’s recommended approach.

69-69: Proper update to vi.fn().
This replacement from jest.fn() to vi.fn() aligns perfectly with the Vitest API.

248-252: Correct transition to vi.mock().
Replacing jest.mock() with vi.mock() ensures that the react-toastify library is mocked using Vitest. Additionally, swapping to vi.fn() for success, warn, and error follows Vitest’s mocking pattern.

279-279: Appropriate usage of vi.clearAllMocks().
Replacing jest.clearAllMocks() with vi.clearAllMocks() ensures that all mock states and call histories are reset between tests under Vitest.

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.

@github-actions GitHub Actions
Copy link

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
Copy link

codecov bot commented Dec 26, 2024 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.39%. Comparing base (89aebba) to head (695f842).
Report is 9 commits behind head on develop-postgres.

Additional details and impacted files 
@@                  Coverage Diff                  @@
##           develop-postgres    #2947       +/-   ##
=====================================================
+ Coverage             46.09%   88.39%   +42.30%     
=====================================================
  Files                   299      316       +17     
  Lines                  7420     8271      +851     
  Branches               1623     1868      +245     
=====================================================
+ Hits                   3420     7311     +3891     
+ Misses                 3765      742     -3023     
+ Partials                235      218       -17

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

@palisadoes palisadoes merged commit 5b3e840 into PalisadoesFoundation:develop-postgres Dec 26, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@palisadoes palisadoes palisadoes approved these changes

@coderabbitai coderabbitai[bot] coderabbitai[bot] approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@gracefullcoder @palisadoes