Skip to content

Fix Sonar coverage reporting in CI - #1392

Merged
LunaUrsa merged 2 commits into
uatfrom
codex/fix-sonar-coverage
Nov 15, 2026
Merged

LunaUrsa merged 2 commits into
uatfrom
codex/fix-sonar-coverage

Conversation

@LunaUrsa

Copy link
Copy Markdown
Contributor

Sonar scans ran without the LCOV report generated by Vitest, leaving coverage at 0%. Both push workflows now upload coverage from the test job, wait for that job, and download and verify the report before scanning. Restore coverage testing on main.

Align Sonar test classification and coverage exclusions with Vitest while preserving broader static analysis. Add regression tests that compare the coverage scopes across application TypeScript files.

Validation:

  • Full Vitest coverage suite passed: 100% lines, statements, and functions; 97.23% branches.
  • TypeScript check, targeted ESLint, workflow YAML/artifact handoff checks, and git diff --check passed.
  • Regression tests and lint rechecked after moving the test into src/vitest on the fresh uat-based branch.
  • Local checks used Node 24.22.0; CI uses .nvmrc. Sonar import will be confirmed after merge and the next push analysis.

@LunaUrsa
LunaUrsa requested a review from a team as a code owner November 14, 2026 20:31
@LunaUrsa
LunaUrsa merged commit 848561e into uat Nov 15, 2026
12 checks passed
@LunaUrsa
LunaUrsa deleted the codex/fix-sonar-coverage branch November 15, 2026 00:04
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.

1 participant