[quality] ratchet up 10 stale Go coverage baselines to actual values#19761
[quality] ratchet up 10 stale Go coverage baselines to actual values#19761kubestellar-hive[bot] wants to merge 1 commit into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for kubestellarconsole canceled.
|
|
👋 Hey @kubestellar-hive[bot] — thanks for opening this PR!
This is an automated message. |
101277f to
5567001
Compare
03962c3 to
a5abaf8
Compare
Updates go-package-coverage-ratchet.txt to reflect actual measured coverage. Many packages had significantly outdated baselines: Supporting packages (12 updates): - pkg/ai: 0.0 → 100.0 - pkg/models: 0.0 → 100.0 - pkg/safego: 65.0 → 100.0 - pkg/stellar: 80.0 → 100.0 - pkg/sanitize: 85.0 → 100.0 - pkg/rewards: 95.0 → 100.0 - pkg/notifications: 75.0 → 78.5 - pkg/watcher: 67.1 → 72.8 - pkg/settings: 75.0 → 77.1 - pkg/kagent: 85.0 → 86.2 - pkg/mcp: 65.0 → 67.2 - pkg/fileutil: 50.0 → 54.2 Compliance packages (16 updates): - 10 packages at 100.0% (were 55-75%): fedramp, hipaa, nist80053, slsa, sbom, signing, licenses, stig, baa, airgap, frameworks, reports - pkg/gxp: 60.0 → 98.0 - pkg/changecontrol: 60.0 → 95.3 - pkg/sod: 60.0 → 88.5 - pkg/residency: 65.0 → 85.5 Stale baselines defeat the purpose of ratcheting — coverage can silently regress back to the old floor without triggering a failure. Signed-off-by: Quality Agent <quality-agent@kubestellar.io>
a5abaf8 to
40d5923
Compare
Test Improvement
Ratchets up 28 stale Go coverage baselines to actual measured values. Many packages were at 100% coverage but the ratchet file listed 0-75%, allowing silent regressions.
Key corrections
All values verified via
go test -cover.Filed by quality agent (hold-gated mode). Human review required.