Configure codecov to check for 100% unit test coverage

[rlskoeser]

Summary by CodeRabbit

• Chores
  • Updated coverage reporting configuration to set separate coverage targets for application and test code. Coverage checks now apply distinct thresholds for source and test files.

[coderabbitai]

Walkthrough

A new codecov.yml configuration file has been added to customize code coverage status checks. The configuration disables the default global check and introduces two specific contexts: one for application code in src/ with a 95% threshold, and another for test code in tests/ with a 100% threshold.

Changes

File(s)	Change Summary
codecov.yml	Added configuration to define separate coverage status checks for application and test code.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant CI
    participant Codecov

    Developer->>CI: Pushes code
    CI->>Codecov: Uploads coverage reports
    Codecov->>CI: Evaluates coverage for "app" (src/) context (95%)
    Codecov->>CI: Evaluates coverage for "tests" (tests/) context (100%)
    CI->>Developer: Reports status for each context

Loading

Poem

Hopping through code with coverage in sight,
Now app and test each have their own light.
Ninety-five for app, a hundred for test—
With yaml in paw, we’re aiming our best!
Two little checks, one big leap,
Coverage dreams for rabbits to keep.
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ec41ca3 and 916ab7f.

📒 Files selected for processing (1)

• codecov.yml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• codecov.yml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

codecov.yml (1)

5-8: Consider setting an explicit coverage threshold and glob pattern for “app”
Using target: auto relies on Codecov’s default (often 80% or the badge-configured value), which may drift over time. Specifying 95% makes your intent explicit. Likewise, updating the path to a glob (src/**) ensures all subdirectories are included.

Diff proposal:

 app:
-  target: auto  # default target (95%)
+  target: 95%  # enforce 95% coverage for application code
-    paths:
-      - "src/"  # limit to files within src code directory
+    paths:
+      - "src/**"  # include all files under src/

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2a7bcc1 and ec41ca3.

📒 Files selected for processing (1)

• codecov.yml (1 hunks)

🔇 Additional comments (2)

codecov.yml (2)

1-4: Disabling default coverage status check intentionally configured
The default: false setting at the project level correctly disables the global status check, allowing you to define fine-grained contexts below.

---

9-12: Verify the “test/” path and 100% threshold for tests context
Requiring 100% coverage on the test code itself is unusual since test files rarely invoke all their own lines (and may not be imported). Please confirm:

1. Your test directory is actually named test/ (not tests/).
2. That Codecov counts test-file coverage as expected.

If the directory is tests/, update the path accordingly.