Refactor use session to vitest

[vivekbisen04]

What kind of change does this PR introduce?

Refactoring - Converting test file from Jest to Vitest testing framework

Issue Number:

Fixes #2754

Did you add tests for your changes?

Yes. The entire PR is focused on refactoring existing tests from Jest to Vitest while maintaining 100% test coverage.

Snapshots/Videos:

If relevant, did you update the documentation?

N/A - This change is focused on test infrastructure and doesn't require documentation updates.

Summary

This PR refactors the test file src/utils/useSession.test.tsx to use Vitest instead of Jest as part of our ongoing testing framework migration. The changes include:

• Renaming the file from useSession.test.tsx to useSession.spec.tsx
• Replacing Jest-specific syntax and mocks with Vitest equivalents
• Ensuring all existing test cases are properly migrated
• Maintaining 100% test coverage for the file
• Following Vitest best practices and conventions

The motivation is to standardize our testing framework across the codebase by moving from Jest to Vitest, which offers better performance and integration with our tooling.

Does this PR introduce a breaking change?

No. This is an internal refactor of test code and doesn't affect the production code or its behavior.

Summary by CodeRabbit

• Tests
  • Introduced a comprehensive suite of tests for the session management functionality.
  • Validated behavior under various scenarios including session timeout handling and event listener management.
  • Ensured proper error handling and session extension processes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request focuses on refactoring the src/utils/useSession.spec.tsx test file from Jest to Vitest. The changes involve comprehensive test suite development for the useSession hook, utilizing the @testing-library/react and vitest frameworks. The tests cover various scenarios including session management, timeout handling, event listener registration, error handling, and session extension, ensuring thorough validation of the hook's functionality.

Changes

File	Change Summary
src/utils/useSession.spec.tsx	Migrated test file from Jest to Vitest, added comprehensive test cases for useSession hook covering session management, timeout handling, and error scenarios

Assessment against linked issues

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

Possibly related issues

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

Possibly related PRs

• added vitest to chat.jsx #2649: Refactoring Chat component tests to Vitest
• Add AdvertisementEntry.spec.tsx for Vitest migration #2680: Migrating AdvertisementEntry component tests to Vitest
• Refactor: test from jest to vitest #2688: Refactoring Groups component tests to Vitest

Suggested labels

refactor

Suggested reviewers

• palisadoes

Poem

🐰 In the realm of code, a hook takes flight,
Vitest's magic brings testing delight!
Sessions dance, timers tick with grace,
Refactored tests leave no trace
Of Jest's old, weary embrace! 🧪✨

---

📜 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 0cede94 and 9419099.

📒 Files selected for processing (1)

• src/utils/useSession.spec.tsx (1 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

• 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