Skip to content

docs: add backend coverage reporting#414

Closed
saurabhhhcodes wants to merge 1 commit into
Kuldeeep18:mainfrom
saurabhhhcodes:codex/coverage-reporting
Closed

docs: add backend coverage reporting#414
saurabhhhcodes wants to merge 1 commit into
Kuldeeep18:mainfrom
saurabhhhcodes:codex/coverage-reporting

Conversation

@saurabhhhcodes

Copy link
Copy Markdown
Contributor

What changed

  • Added coverage to the project requirements.
  • Added a backend .coveragerc that excludes migrations and virtual environments.
  • Documented the local coverage workflow in CONTRIBUTING.md.

Why

  • Contributors need a simple, repeatable way to measure which backend areas are covered by tests.
  • This makes it easier to spot missing coverage before opening a PR.

Validation

  • git diff --check

Closes #391

@coderabbitai

coderabbitai Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4ac5eabf-0e8c-479f-a917-1814b505b18b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@Kuldeeep18 Kuldeeep18 closed this Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

LO-054 [Easy]: Add Code Coverage Reports to Backend Test Suite

2 participants