Track Sonar coverage-wiring gap in dev-notes - #5
Conversation
Document that SonarCloud QG fails on new-code coverage because CI does not upload XCTest/xccov yet — known craft debt, not a Gate 2 failure. Co-authored-by: Rik Dryfoos <rdryfoos@users.noreply.github.com>
Co-authored-by: Rik Dryfoos <rdryfoos@users.noreply.github.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe development notes document that CI does not publish Swift test coverage to SonarCloud. They record the resulting 0.0% coverage report and clarify that the 80% “Coverage on New Code” threshold remains unmet outside Phase E scope. ChangesSonarCloud coverage readiness
Estimated code review effort: 1 (Trivial) | ~2 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|



Summary
Documents the standing SonarCloud Quality Gate failure (
0.0% Coverage on New Code) as known craft debt inspecs/001-mvp/dev-notes.mdPlatform readiness — CI does not yet publish XCTest/xccov into Sonar.Why
Interview / review honesty: the red
SonarCloud Code Analysischeck is explained and tracked in-repo, not mistaken for a Gate 2 or product failure.Traces
Craft / platform backlog only (no PRD AC). Related context: Phase E Sonar CI (T089).
Test plan
Summary by CodeRabbit