Repository navigation
ci: add coverage gates for critical reliability modules #219
Description
Source
Extracted from the reliability audit snippet: run coverage tooling and ensure error/edge paths are covered, not only happy paths.
Programmatic test scope
Add coverage gates for critical modules beyond the existing general coverage reporting.
Modules to consider
src/wal.rssrc/db.rstransaction and checkpoint pathssrc/storage/persistent_facts.rssrc/storage/btree_v6.rssrc/query/datalog/executor.rssrc/query/datalog/evaluator.rssrc/query/datalog/stratification.rs
Acceptance criteria
- CI reports per-module line and/or branch coverage.
- Thresholds are realistic and ratcheted over time.
- Error-path tests count toward the target; generated reports are easy to inspect.
Activity
adityamukho commentedon May 15, 2026
Prerequisites
This issue should be scheduled last in the reliability/testing cluster — after the reliability test suites it is meant to gate on actually exist. Setting coverage thresholds before these suites land would measure an artificially incomplete baseline and produce ratchet values that have to be revised immediately.
chore(wave3): foundation — FaultInjectingBackend, fuzz/ crate, propte…
docs: fix swapped issue numbers in Wave 3 PR4 and PR6 plans