ci: measure and publish coverage - #57
Merged
Merged
Conversation
Codacy carries a 60% coverage goal that has always read "not reported", because nothing ever produced a report. Measured: 51% overall. A separate, deliberately non-blocking job. It re-runs the four suites under tracing, which is slower, and the gate job should stay the fast answer — so this one only measures and never decides pass/fail. The summary lands in the job summary and coverage.xml/coverage.txt upload as artifacts. Where the misses are, for anyone reading the number: app.py 43% and ssh_manager.py 55% are mostly install/bootstrap and remote-management paths that need a real host to exercise, which is why they are low and why chasing the percentage for its own sake would be the wrong instinct. manage.py is 0% — the break-glass CLI a locked-out admin uses, and a genuine gap. auth.py 87% and models.py 90% are where this session's tests landed. Codacy upload needs a CODACY_PROJECT_TOKEN this repo does not have, so the step is present but commented out with the instructions rather than half-wired into a job that would fail on the missing secret. Verified by running the job's exact commands locally: 4 suites traced, combined, valid Cobertura XML out. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Up to standards ✅🟢 Issues
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codacy carries a 60% coverage goal that has always read "not reported", because nothing ever produced a report.
Measured: 51% overall.
A separate, non-blocking job. It re-runs the four suites under tracing, which is slower, and the gate job should stay the fast answer — so this one only measures and never decides pass/fail. The table lands in the job summary;
coverage.xmlandcoverage.txtupload as artifacts.Where the misses actually are
Worth saying, so the number isn't read as worse than it is:
app.pyat 43% andssh_manager.pyat 55% are largely install, bootstrap and remote-management paths that need a real host to exercise. Chasing the percentage there for its own sake would be the wrong instinct.manage.pyat 0% is the interesting one — that's the break-glass CLI a locked-out admin uses to reset a password or disable 2FA. A genuine gap, and a good next target.auth.py87% andmodels.py90% are where this session's tests landed.Codacy upload
Needs a
CODACY_PROJECT_TOKENthis repo doesn't have. The step is present but commented out with the instructions, rather than half-wired into a job that would fail on a missing secret. Add the secret and uncomment two lines to turn it on.Verified by running the job's exact commands locally — 4 suites traced, combined, valid Cobertura XML out.
🤖 Generated with Claude Code