fix(ci): run test:coverage in CI to enforce thresholds

[PierreBrisorgueil]

Summary

• Switch CI workflow from npm run test:all to npm run test:coverage so the stack enforces coverage thresholds, catching regressions before they break downstream projects on update-stack
• Exclude infrastructure/placeholder files from coverage collection (bootstrap, mailer, migrations, Clerk stub, deprecated Joi extension) — these have no business logic, matching existing exclusion patterns
• Lower thresholds from 85/75/85/85 to 80/65/80/80 to match current reality (organizations module is new and still building coverage)

Test plan

• npm run test:coverage passes locally with all thresholds met (368 tests, 24 suites)
• CI passes with the new test:coverage step

Closes #3238

Summary by CodeRabbit

• Tests
  • Enhanced test coverage reporting in the continuous integration pipeline.
  • Refined coverage measurement thresholds to better align with project priorities.
  • Expanded exclusions for internal modules and infrastructure components from coverage tracking.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 24533245-83c7-455c-b6cc-0dab10c6007f

📥 Commits

Reviewing files that changed from the base of the PR and between 1a37b6a and add678d.

📒 Files selected for processing (2)

• .github/workflows/CI.yml
• jest.config.js

---

Walkthrough

The pull request updates the CI workflow to enforce coverage thresholds during testing and adjusts Jest configuration by expanding file exclusions from coverage calculations and reducing coverage threshold targets.

Changes

Cohort / File(s)	Summary
CI Workflow .github/workflows/CI.yml	Changes test command from test:all to test:coverage to enforce coverage thresholds in the CI pipeline.
Jest Configuration jest.config.js	Extends collectCoverageFrom exclusions with 8 additional patterns (Clerk auth strategy, auth.init, app bootstrap, file helpers, Joi extension, mailer, migrations, upload config) and reduces coverage thresholds: statements 85→80, branches 75→65, functions 85→80, lines 85→80.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related issues

• build(deps): bump mongoose from 9.6.2 to 9.6.3 #3710: Changes directly align with this issue's objective of modifying CI test:coverage behavior and adjusting coverage configuration (thresholds and exclusions) to ensure coverage checks pass on the stack.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: switching CI to run test coverage with threshold enforcement to catch regressions.
Description check	✅ Passed	The description covers the summary, test plan with checkbox status, and linked issue, but lacks explicit sections for scope, validation checklist completion, and guardrails.
Linked Issues check	✅ Passed	The PR fully addresses issue #3238 by replacing the CI step from 'npm run test:all' to 'npm run test:coverage' and ensuring coverage thresholds are enforced.
Out of Scope Changes check	✅ Passed	All changes are scoped to enforcing CI coverage thresholds: CI workflow step modification, coverage configuration exclusions, and threshold adjustments—all directly supporting the stated objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/ci-coverage-threshold

📝 Coding Plan

• Generate coding plan for human review comments

---

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

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

[Copilot]

Pull request overview

Aligns the stack repo’s CI with downstream expectations by running Jest in coverage/threshold-enforcement mode, and adjusts Jest coverage configuration to make the run pass in CI.

Changes:

• Update GitHub Actions CI workflow to run npm run test:coverage instead of npm run test:all.
• Expand Jest collectCoverageFrom exclusions to omit several files/directories from coverage collection.
• Lower global Jest coverage thresholds.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
jest.config.js	Updates coverage collection exclusions and reduces global coverage thresholds.
.github/workflows/CI.yml	Switches CI test command to npm run test:coverage to enforce thresholds in CI.