Refactor: Migrated src/components/CurrentHourIndicator/CurrentHourIndicator.test.tsx from Jest to Vitest

[subrajeet-maharana]

What kind of change does this PR introduce?

This PR will migrate the src/components/CurrentHourIndicator/CurrentHourIndicator.test.tsx from Jest to Vitest.

Issue Number:

Fixes #2840

Did you add tests for your changes?

No

Snapshots/Videos:

If relevant, did you update the documentation?
N/A

Summary

Does this PR introduce a breaking change?
No

Other information
N/A

Have you read the contributing guide?

Yes

Summary by CodeRabbit

Summary by CodeRabbit

• New Features

  • Simplified the structure of the schemas array in the tag template for improved readability.

• Tests

  • Enhanced test suite for the CurrentHourIndicator component with new import statements for better structuring of test cases.

• Chores

  • Updated dependencies in package.json for various libraries.

[coderabbitai]

Walkthrough

The pull request involves two primary changes: a modification to the tagTemplate object in src/components/CheckIn/tagTemplate.ts and an update to the test file src/components/CurrentHourIndicator/CurrentHourIndicator.spec.tsx. In the tagTemplate.ts file, the schemas array structure has been simplified, changing from an array of objects to a single object with a name property. The CurrentHourIndicator test file has been updated to use Vitest testing framework imports.

Changes

File	Change Summary
src/components/CheckIn/tagTemplate.ts	Simplified schemas array structure, converting from nested array to a single object with name property
src/components/CurrentHourIndicator/CurrentHourIndicator.spec.tsx	Added Vitest imports: describe, test, and expect

Assessment against linked issues

Objective	Addressed	Explanation
Refactor CurrentHourIndicator test from Jest to Vitest [#2840]	✅
Rename test file to .spec.* suffix [#2840]	✅

Possibly related issues

• Refactor: src/components/AddOn/support/components/MainContent/MainContent.test.tsx from Jest to Vitest #2475: Refactoring another component test from Jest to Vitest
• Refactor : src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.test.tsx from Jest to Vitest #2493: Similar Vitest migration for ChangeLanguageDropdown component
• Refactor : src/components/CheckIn/CheckInModal.test.tsx from Jest to Vitest #2494: Vitest migration for CheckInModal test
• Refactor : src/components/CheckIn/CheckInWrapper.test.tsx from Jest to Vitest #2495: Vitest migration for CheckInWrapper test

Possibly related PRs

• Refactor : src/components/CheckIn/CheckInWrapper.test.tsx from Jest to Vitest #2709: Refactoring CheckInWrapper tests to Vitest
• Refactor Tests: Migrate src/screens/UserPortal/UserScreen/UserScreen.tsx from Jest to Vitest #2632: Migrating UserScreen component tests to Vitest
• refactor:vitest to MemberDetailScreen #2662: Migrating MemberDetailScreen component tests to Vitest

Suggested reviewers

• palisadoes

Poem

🐰 Hop, hop, testing we go!
From Jest to Vitest, watch our code flow
Schemas simplified, imports anew
Testing magic, our framework true
Rabbit's testing dance, oh so bright! 🧪

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

📜 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 9772f7d and 9efcd4e.

📒 Files selected for processing (2)

• src/components/CheckIn/tagTemplate.ts (2 hunks)
• src/components/CurrentHourIndicator/CurrentHourIndicator.spec.tsx (1 hunks)

🧰 Additional context used

🪛 GitHub Check: Performs linting, formatting, type-checking, checking for different source and target branch

src/components/CheckIn/tagTemplate.ts

[failure] 6-6:
Object literal may only specify known properties, and 'name' does not exist in type 'objectOutputType<{ name: ZodString; type: ZodString; content: ZodOptional; position: ZodObject<{ x: ZodNumber; y: ZodNumber; }, "strip", ZodTypeAny, { ...; }, { ...; }>; ... 7 more ...; __isSplit: ZodOptional<...>; }, ZodTypeAny, "passthrough">[]'.

🔇 Additional comments (1)

src/components/CurrentHourIndicator/CurrentHourIndicator.spec.tsx (1)

4-4: All Good with Vitest Import

The migration from Jest to Vitest is correct here, and the tests appear to remain functional.

---

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

[palisadoes]

Please merge your local branch with the latest upstream. That should fix the error