fix: Update regex to detect all variants of /* istanbul ignore */ comments #3217

[khushipatil1523]

Issue Number:

Fixes #3211

Description:
What Changed:
The regular expression in the code_coverage_disable_check.py script has been updated to ensure that all variants of the /* istanbul ignore / comment are detected. This includes:
/ istanbul ignore /
/ istanbul ignore next /
/ istanbul ignore line /
/ istanbul ignore next -- @preserve */

Snapshots/Videos: dummy test files to check that its working or not

If relevant, did you update the documentation?

N/A

Does this PR introduce a breaking change?

No

Other information

N/A

Summary by CodeRabbit

• Tests

  • Updated test suite for Posts component from Jest to Vitest
  • Improved test mocking and isolation techniques
  • Enhanced test case clarity and maintainability

• Chores

  • Updated code coverage detection script to handle more comment variations

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request encompasses two primary changes: an update to the code coverage disable check script's regular expression pattern and a migration of the Posts.spec.tsx test file from Jest to Vitest. The code coverage script modification enhances the detection of code coverage disable statements, while the test file refactoring updates the testing framework to use Vitest's syntax and mocking methods.

Changes

File	Change Summary
.github/workflows/scripts/code_coverage_disable_check.py	Updated regex pattern to include optional comments after next or -line keywords
src/screens/UserPortal/Posts/Posts.spec.tsx	Migrated from Jest to Vitest, updated mocking methods and test hooks

Assessment against linked issues

Objective	Addressed	Explanation
Refactor from Jest to Vitest [#3211]	✅
Replace Jest-specific functions with Vitest equivalents	✅
Rename test file suffix	✅
Maintain 100% test coverage	❓	Coverage verification not visible in the diff

Possibly related issues

• Fix .github/workflows/scripts/code_coverage_disable_check.py #3217: Relates to improving the code coverage disable check script, which aligns with the regex pattern modification in this PR
• Refactor: src/screens/UserPortal/Posts from Jest to Vitest #2578: Involves refactoring the Posts test file from Jest to Vitest, directly connected to this PR's changes

Possibly related PRs

• feat!: Migrate Testing Framework from Jest to Vitest #2457: Base Vitest configuration PR
• Refactor: src/screens/UserPortal/Posts from Jest to Vitest #2578 #3190: Similar Jest to Vitest refactoring
• refactored src/screens/FundCampaignPledge from jest to vitest #3208: Vitest testing framework migration

Suggested labels

test, ignore-sensitive-files-pr

Suggested reviewers

• palisadoes

Poem

🐰 In the realm of code, a rabbit's delight,
Jest transforms to Vitest, tests shine bright!
Regex patterns dance, coverage takes flight,
Mocking methods shift with playful might,
A testing journey of pure code insight! 🧪

---

📜 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 5893198 and 35d314a.

📒 Files selected for processing (2)

• .github/workflows/scripts/code_coverage_disable_check.py (1 hunks)
• src/screens/UserPortal/Posts/Posts.spec.tsx (6 hunks)

Finishing Touches

• 📝 Generate Docstrings

---

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