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

Refactored src/components/ProfileDropdown/ from Jest to Vitest #2922

Merged

Conversation

syedali237
Copy link
Contributor

@syedali237 syedali237 commented Dec 26, 2024

What kind of change does this PR introduce?

Refactoring & Testing

Issue Number:

Fixes #2819

Did you add tests for your changes?

Yes

Snapshots/Videos:

Screenshot 2024-12-26 at 4 03 41 PM

If relevant, did you update the documentation?

No

Summary

Migrated ProfileDropdown.test.tsx to ProfileDropdown.spec.tsx (i.e. from jest to vitest), and added new tests to ensure 100% coverage.

Does this PR introduce a breaking change?

No

Other information

N/A

Have you read the contributing guide?

Yes

Summary by CodeRabbit

  • Tests
    • Enhanced test suite for the ProfileDropdown component with improved error handling and navigation checks.
    • Integrated new testing utilities for better asynchronous operation handling.
    • Updated mock functions for navigation and notifications to improve test accuracy.
    • Added test cases for user role-based navigation and error logging during logout.

Copy link
Contributor

coderabbitai bot commented Dec 26, 2024

Walkthrough

The pull request focuses on refactoring the test suite for the ProfileDropdown component from Jest to Vitest. The changes involve updating the testing framework, replacing Jest-specific functions with Vitest equivalents, and renaming the test file from .test.tsx to .spec.tsx. The modifications include adding mocks for useNavigate and react-toastify, improving asynchronous operation handling, and enhancing test coverage for navigation and error scenarios.

Changes

File Change Summary
src/components/ProfileDropdown/ProfileDropdown.spec.tsx - Replaced Jest mocking with Vitest mocks
- Added mockNavigate function
- Updated react-toastify mock
- Integrated waitFor for async operations
- Added new test cases for error handling and navigation

Assessment against linked issues

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

Possibly related issues

Possibly related PRs

Suggested reviewers

  • palisadoes

Poem

🐰 In the realm of tests, a rabbit's delight,
Jest fades away, Vitest shines bright
ProfileDropdown dances with merry glee
Async and mock, now running free
Code refactored, coverage complete! 🧪✨


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

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/components/ProfileDropdown/ProfileDropdown.spec.tsx (1)

75-75: Duplicate afterEach blocks detected.
Both afterEach calls invoke vi.clearAllMocks() and localStorage.clear(), which can be merged to avoid potential confusion or maintenance overhead. Consider consolidating them into a single afterEach block if there's no functional need for duplication.

-afterEach(() => {
-  vi.clearAllMocks();
-  localStorage.clear();
-});
-afterEach(() => {
-  vi.clearAllMocks();
-  localStorage.clear();
-});
+afterEach(() => {
+  vi.clearAllMocks();
+  localStorage.clear();
+});

Also applies to: 79-79

📜 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 a378517.

📒 Files selected for processing (1)
  • src/components/ProfileDropdown/ProfileDropdown.spec.tsx (4 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/ProfileDropdown/ProfileDropdown.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 (13)
src/components/ProfileDropdown/ProfileDropdown.spec.tsx (13)

2-2: Looks good: Implementation aligns with Vitest imports.
This import from @testing-library/react is essential for asynchronous operations and DOM querying in the new testing environment.


12-12: Properly switched from Jest to Vitest.
Using vi from vitest is the recommended approach for mocking when refactoring test cases from Jest to Vitest.


15-15: Local storage usage is consistent.
Retrieving setItem directly from the custom hook is convenient and keeps test setup straightforward.


16-16: Valid approach to mock navigation.
Defining mockNavigate with vi.fn() ensures we properly track route transitions.


18-25: Correctly mocking react-router-dom.
Spreading in the actual module and overriding useNavigate is a standard pattern for controlling navigation in tests.


53-59: Good mock for react-toastify.
Replacing the Jest mock with Vitest's vi.mock approach is correct for ensuring consistent behavior across all toast calls.


145-147: Clear test setup for user roles.
Ensuring SuperAdmin is false and AdminFor is empty sets up a clean baseline for member testing.


151-153: i18n wrapping is correct.
Wrapping the component with the I18nextProvider is essential for verifying localized strings in tests.


162-164: Asynchronous click handling is correct.
Using act around userEvent.click ensures that all effects and state updates occur before assertions.


166-167: Verifies navigation to /user/settings.
This test confirms that non-admin users are directed to the correct route.


170-214: Error revoking refresh token is handled properly.
The test ensures the console error is logged, improving coverage for the negative path.


217-239: Validates user navigation path again.
This double-check ensures no regressions in user flow when repeated with different localStorage states.


241-263: Correct route verification for admins.
The test covers the scenario for admin users navigating to '/member/:userID'.

Copy link

codecov bot commented Dec 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.00%. Comparing base (35cce16) to head (a378517).
Report is 10 commits behind head on develop-postgres.

Additional details and impacted files
@@                  Coverage Diff                  @@
##           develop-postgres    #2922       +/-   ##
=====================================================
+ Coverage             58.52%   88.00%   +29.48%     
=====================================================
  Files                   299      316       +17     
  Lines                  7414     8265      +851     
  Branches               1621     1810      +189     
=====================================================
+ Hits                   4339     7274     +2935     
+ Misses                 2828      780     -2048     
+ Partials                247      211       -36     

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

Copy link
Contributor

@palisadoes palisadoes left a comment

Choose a reason for hiding this comment

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

Thanks for adding the extra test cases

@palisadoes palisadoes merged commit 13f16b9 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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants