| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | fix: exclude generated package files from coverage summary | Craig Jennings | 36 hours | 1 | -3/+7 |
| | | | | | | | undercover never instruments generated files like NAME-autoloads.el and NAME-pkg.el, so they have no report entry. The file-weighted summary counted each as untested at 0% and dragged the project number down (97.2% read as 72.9% after eask generated the autoloads file). Drop NAME-autoloads.el and NAME-pkg.el from the source-file scan. A genuinely untested source is still flagged. Only the build-generated files are skipped. | ||||
| * | test: add make coverage-summary with untested-module detection | Craig Jennings | 42 hours | 1 | -0/+173 |
| A module no test loads never appears in undercover's report, so a line-weighted total silently skips it. The coverage-summary target counts such a file as 0% and weights the project number by file, so untested modules stay visible. I replaced scripts/coverage-summary.py, which only summarized files already in the report. make coverage now chains the summary, and CI prints it in the coverage step instead of a separate python call. The helper runs on stock Emacs (built-in json and seq), so it needs no dev deps. It lives in tracked scripts/ so CI can reach it. | |||||
