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

Refactor : Added Vitest to Requests Screen #2654

Conversation

shivasankaran18
Copy link
Contributor

@shivasankaran18 shivasankaran18 commented Dec 13, 2024

What kind of change does this PR introduce?

Added Vitest to Requests Screen

Issue Number: 2569

Fixes #2569

Did you add tests for your changes?
Yes

Snapshots/Videos:
Screenshot 2024-12-13 175144

If relevant, did you update the documentation?

Summary

Migrated the testing framework to Vitest.
Updated all test files and configurations to be compatible with Vitest's syntax and features.

Have you read the contributing guide?

Yes

Summary by CodeRabbit

  • Tests
    • Enhanced testing environment with vitest library for mocking localStorage and window.location.
    • Introduced a new utility function wait for improved asynchronous testing.
    • Updated test cases to cover various scenarios for the Requests component while preserving existing structure.

Copy link
Contributor

coderabbitai bot commented Dec 13, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request modifies the Requests.spec.tsx test file by integrating the vitest library for mocking global functions, specifically localStorage and window.location. It introduces a new utility function, wait, to facilitate asynchronous testing. The test structure remains largely unchanged, but the enhancements improve the testing environment, ensuring robust coverage of the Requests component under various conditions.

Changes

File Change Summary
src/screens/Requests/Requests.spec.tsx Added vitest for mocking localStorage and window.location, introduced wait utility function, and maintained test structure.

Assessment against linked issues

Objective Addressed Explanation
Replace Jest-specific functions and mocks with Vitest equivalents (#2569)
Ensure all tests in src/screens/Requests pass after migration (#2569) Test results are not provided in the PR.
Maintain the test coverage for the file as 100% after migration (#2569) Coverage details are not included in the PR.
Upload a video or photo for this specific file coverage (#2569) No video or photo uploaded in the PR.

Possibly related PRs

Suggested labels

refactor

Suggested reviewers

  • pranshugupta54
  • varshith257

Poem

In the land of tests, we hop and play,
With Vitest in hand, we brighten the day.
Mocking and waiting, our tests now shine,
As we leap through code, all errors decline.
So here's to the changes, both clever and bright,
A rabbit's delight in the coding night! 🐇✨


📜 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 aceed4c and bb4bad8.

📒 Files selected for processing (1)
  • src/screens/Requests/Requests.spec.tsx (2 hunks)

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. (Experiment)
  • @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: 1

🧹 Outside diff range and nitpick comments (2)
src/screens/Requests/Requests.spec.tsx (2)

25-34: Enhance localStorage mock implementation.

While the basic methods are correctly stubbed, consider these improvements:

  1. Add the length property to match the Web Storage API specification
  2. Enhance the JSDoc comment to include example usage and return types
 /**
  * Set up `localStorage` stubs for testing.
+ * 
+ * @example
+ * localStorage.getItem('key') // Returns undefined by default
+ * localStorage.setItem('key', 'value') // Returns undefined
  */
 vi.stubGlobal('localStorage', {
   getItem: vi.fn(),
   setItem: vi.fn(),
   clear: vi.fn(),
   removeItem: vi.fn(),
+  length: 0,
 });

54-61: Consider moving wait utility to shared test utilities.

The wait utility function is well-implemented, but it could be beneficial to move it to a shared test utilities file since it's a generic helper that could be useful in other test files.

Consider:

  1. Moving this function to src/utils/testUtils.ts
  2. Exporting it alongside other test utilities
  3. Making the default timeout configurable through an environment variable for CI environments
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a5c9d97 and aceed4c.

📒 Files selected for processing (1)
  • src/screens/Requests/Requests.spec.tsx (2 hunks)
🔇 Additional comments (2)
src/screens/Requests/Requests.spec.tsx (2)

23-24: LGTM: Vitest import is correctly implemented.

The import of vi from 'vitest' is properly placed and follows Vitest's best practices.


Line range hint 1-300: Overall test implementation looks solid!

The test suite demonstrates:

  • Comprehensive coverage of different scenarios
  • Proper async handling with act()
  • Good cleanup practices
  • Appropriate use of Vitest features

The migration to Vitest has been implemented successfully while maintaining the existing test coverage.

Comment on lines 36 to 42
/**
* Mock `window.location` for testing redirection behavior.
*/

Object.defineProperty(window, 'location', {
value: { href: 'http://localhost/', assign: vi.fn(), reload: vi.fn() },
});
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Enhance window.location mock implementation.

The current implementation could be improved to better match the Window.Location interface:

 /**
  * Mock `window.location` for testing redirection behavior.
+ * 
+ * @example
+ * window.location.href = '/new-path'
+ * expect(window.location.pathname).toBe('/new-path')
  */
 Object.defineProperty(window, 'location', {
   value: {
     href: 'http://localhost/',
     assign: vi.fn(),
     reload: vi.fn(),
+    pathname: '/',
+    search: '',
+    hash: '',
+    origin: 'http://localhost',
   },
 });
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
/**
* Mock `window.location` for testing redirection behavior.
*/
Object.defineProperty(window, 'location', {
value: { href: 'http://localhost/', assign: vi.fn(), reload: vi.fn() },
});
/**
* Mock `window.location` for testing redirection behavior.
*
* @example
* window.location.href = '/new-path'
* expect(window.location.pathname).toBe('/new-path')
*/
Object.defineProperty(window, 'location', {
value: {
href: 'http://localhost/',
assign: vi.fn(),
reload: vi.fn(),
pathname: '/',
search: '',
hash: '',
origin: 'http://localhost',
},
});

Copy link

codecov bot commented Dec 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.78%. Comparing base (a5c9d97) to head (bb4bad8).

Additional details and impacted files
@@                  Coverage Diff                  @@
##           develop-postgres    #2654       +/-   ##
=====================================================
- Coverage             94.55%   83.78%   -10.77%     
=====================================================
  Files                   295      312       +17     
  Lines                  7036     8118     +1082     
  Branches               1516     1830      +314     
=====================================================
+ Hits                   6653     6802      +149     
- Misses                  177     1171      +994     
+ Partials                206      145       -61     

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

@palisadoes
Copy link
Contributor

We have a policy of unassigning contributors who close PRs without getting validation from our reviewer team. This is because:

  1. We start looking for people to review PRs when you submit them.
  2. We often contact them and link to the PR. If the PR is closed the whole effort is wasted.
  3. The historical thread of reviewer comments is broken when the work is spread across multiple PRs. The quality of our code is affected negatively.

Please be considerate of our volunteers' limited time and our desire to improve our code base.

This policy is stated as a pinned post in all our Talawa repositories. Our YouTube videos explain why this practice is not acceptable to our Community.

Unfortunately, if this continues we will have to close the offending PR and unassign you from the issue.

image

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