From 77fe06b0c6f01d1d76bdf503c1b12286ac29aa0a Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Tue, 5 May 2026 03:10:50 -0500 Subject: build: add make coverage target via undercover I want to track test coverage as I work through the upstream issue backlog, so I added an undercover-based flow that mirrors how `make test-unit` already runs each file in its own Cask Emacs process. The Makefile gets `make coverage` and `make coverage-clean`. A new helper at `tests/run-coverage-file.el` instruments `org-drill.el` before the source is loaded. Undercover merges per-file results into a single simplecov JSON at `.coverage/simplecov.json`. I added `undercover` as a Cask development dep and `.coverage/` to `.gitignore` so the report stays local. I also renamed `make install` to `make setup`. The old name read like "deploy the package onto my system," but the target only installs Cask deps into the local `.cask/` directory. `setup` is closer to what it actually does, and all the internal `: install` prerequisites move with it. Baseline at this commit is 10.8% (208/1928 lines on org-drill.el). --- Cask | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'Cask') diff --git a/Cask b/Cask index 5eaf201..c9ebcb2 100644 --- a/Cask +++ b/Cask @@ -6,6 +6,7 @@ (package-file "org-drill.el") (development - (depends-on "assess")) + (depends-on "assess") + (depends-on "undercover")) (depends-on "org" "9.2") -- cgit v1.2.3