Refactored src/utils/convertToBase64.test.ts from Jest to Vitest

[AceHunterr]

What kind of change does this PR introduce?
Refactoring

Issue Number:

Fixes #2759

Did you add tests for your changes?
No

Snapshots/Videos:
Modified the file and ran the npm run test:vitest command to check and it was cleared:

Also ran the specific file vitest npx vitest run .\src\utils\convertToBase64.spec.ts:

And ensured the linting and formatting:

If relevant, did you update the documentation?
Not yet

Summary

Does this PR introduce a breaking change?
No... it simply converts one test suite framework to other.

Other information
Have checked all the points in the Acceptance Criteria that was asked in the Issue:

1. Replaced Jest-specific functions and mocks with Vitest equivalents
2. Renamed the test file from src/utils/convertToBase64.test.ts to src/utils/convertToBase64.spec.ts
3. Ensured all tests in the file pass after migration using npm run test:vitest
4. Maintained the test coverage for the file as 100% after migration as shown in the uploaded snapshot.
5. Upload snapshots for this specific file coverage is 100% in the PR description.

Have you read the contributing guide?
Yes

Summary by CodeRabbit

• Tests
  • Introduced a new test suite for the base64 conversion functionality.
  • Updated error handling tests to improve robustness and accuracy.

[coderabbitai]

Walkthrough

The pull request involves refactoring the convertToBase64 test suite from Jest to Vitest in the src/utils/convertToBase64.spec.ts file. The changes include updating the import statements to use Vitest's testing functions, replacing Jest-specific mocking with Vitest's vi mocking, and ensuring the test cases cover various scenarios for the base64 conversion function.

Changes

File	Change Summary
src/utils/convertToBase64.spec.ts	- Replaced Jest imports with Vitest imports - Updated test cases to use vi for mocking - Added mockFileReader.mockRestore() for cleanup

Assessment against linked issues

Objective	Addressed	Explanation
Replace Jest-specific functions with Vitest equivalents [#2759]	✅
Rename test file from .test.* to .spec.* [#2759]	✅
Ensure tests pass using npm run test:vitest [#2759]	❓	Requires actual test run verification
Maintain 100% test coverage [#2759]	❓	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/AddOn/support/components/MainContent/MainContent.test.tsx from Jest to Vitest #2475: Vitest migration for MainContent.test.tsx
• Refactor: src/components/AddOn/support/services/Plugin.helper.test.ts from Jest to Vitest #2477: Vitest migration for Plugin.helper.test.ts
• Refactor : src/components/CheckIn/CheckInModal.test.tsx from Jest to Vitest #2494: Vitest migration for CheckInModal.test.tsx

Possibly related PRs

• convert from jest to vitest #2486 #2705: Transition from Jest to Vitest
• Refactor : src/components/CheckIn/CheckInWrapper.test.tsx from Jest to Vitest #2709: Migration to Vitest
• Refactor: jest to vitest of itemDeleteModal : fixes #2557 #2713: Refactoring tests to Vitest
• refactor: jest to vitest of itemUpdateStatusModal : fixes #2557 #2714: Updating testing framework
• Refactor: jest to vitest of itemModal : fixes #2557 #2715: Standardizing testing with Vitest

Suggested reviewers

• palisadoes

Poem

🐰 In the realm of code, a test suite transforms,
From Jest's old ways to Vitest's new norms.
Base64 conversion, now crystal clear,
With mocking magic and coverage dear.
A rabbit's leap towards testing delight! 🧪

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 b465221 and 27bd20c.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• src/utils/convertToBase64.spec.ts (3 hunks)

🔇 Additional comments (3)

src/utils/convertToBase64.spec.ts (3)

1-1: Great usage of Vitest imports.
Replacing jest with vitest is correctly done here, ensuring the test suite runs under Vitest without issues.

---

20-20: Good practice: Using vi.spyOn() to mock the global FileReader.
This approach correctly isolates and tests the error-handling logic of convertToBase64.

---

33-33: Appropriate cleanup via mockRestore().
Ensuring the FileReader mock is restored helps avoid side effects in subsequent tests.

---

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]

This PR needs to be closed.

The source and target PR branches are the same. This means that our reviewers will not be able to checkout the changes and test on their systems using this methodology which will cause a rejection error:

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Please follow these steps:

1. Create a new branch with a different name in your local repository
   1. Make sure the branch name is named differently from the required target branch in the PR
   2. Use the git checkout -b command to do this.
2. Resubmit your PR

NOTE: We are also only accepting changes based on the develop-postgres branch until further notice.

Closing

[palisadoes]

This was the same reason why your previous PR had to be closed:

• Refactored src/utils/convertToBase64.test.ts from Jest to Vitest  #2777