Skip to content

test: add branch coverage reporting baseline - #35

Merged
fnayou merged 3 commits into
mainfrom
test/coverage-reporting-baseline
Oct 25, 2026
Merged

fnayou merged 3 commits into
mainfrom
test/coverage-reporting-baseline

Conversation

@fnayou

@fnayou fnayou commented Oct 25, 2026 •

Copy link
Copy Markdown
Owner

Summary

python -m coverage run -m unittest discover -v
  └── coverage report --show-missing
      ├── local per-file branch report
      └── GitHub Actions job summary

Adds pinned development coverage tooling, local instructions, and a per-file CI summary. The baseline is module-level; #31's issue comment records candidate core-policy gaps. No threshold set before #32 review.

Closes #31.

Evidence

  • Before: 133 tests ran without line or branch coverage reporting.
  • After: 133 tests pass; ffmpegfyMe.py baseline: 604 statements, 91 missed, 234 branches, 29 partial branches, 84% combined coverage. This is not core-policy-only coverage.

Merge Danger

Door: Two-way

Blast Radius: CI

Changes affect Python test reporting and contributor instructions.

@fnayou
fnayou merged commit b4f4171 into main Oct 25, 2026
2 checks passed
@fnayou
fnayou deleted the test/coverage-reporting-baseline branch October 25, 2026 04:58
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.

Add branch coverage reporting baseline

1 participant