test/private/rackunit.rkt is at 76.8% coverage (69 missed lines), and the misses are exactly the code that runs when a refactoring test fails: the code-block pretty-printing writer and the failure message rendering. The raise-syntax-error paths in test.rkt for unbound or non-statement identifiers are similarly untested. Covering these means meta-tests: deliberately-failing checks run via rackunit's run-test-case with assertions on the failure output.
This is worth more than the coverage points. Reviewers lean on this failure output when reviewing AI-written rule PRs, and right now it's the least-tested part of the test framework itself.
Part of #680.
test/private/rackunit.rktis at 76.8% coverage (69 missed lines), and the misses are exactly the code that runs when a refactoring test fails: thecode-blockpretty-printing writer and the failure message rendering. Theraise-syntax-errorpaths intest.rktfor unbound or non-statement identifiers are similarly untested. Covering these means meta-tests: deliberately-failing checks run via rackunit'srun-test-casewith assertions on the failure output.This is worth more than the coverage points. Reviewers lean on this failure output when reviewing AI-written rule PRs, and right now it's the least-tested part of the test framework itself.
Part of #680.