[ CI QUALITY LEDGER ]
The ledger your CI reports to.
Elyseum stores normalized test and coverage facts per commit and turns them into history you can read: regressions, recoveries, trends, failed tests, coverage deltas. Per project, per branch, per attempt.
Self-hosted. No vendor lock-in.
Coverage on this commit regressed against the previous comparable run — called out, with the failing tests, on the run page.
[ LEDGER ]
One record per run
Test totals, failures, and line, function, branch, and diff coverage — normalized into a versioned envelope, stored per commit, branch, and attempt.
[ REGRESSIONS ]
History that calls out change
Each run is compared against its previous comparable baseline: regressions and recoveries are named, reruns stay distinct, trends accumulate.
[ DIFF COVERAGE ]
Changed lines, gated in CI
Diff coverage counts only the lines you added, with quality gates that warn or fail the job — reported as a PR comment and a check run.
[ HOW IT WORKS ]
01
Your CI runs its tests and coverage tools, then the elyseum-cli producer — directly or via the GitHub Action — reads the reports.
02
The producer emits the versioned result envelope — a stable schema the host owns, so producers and host stay compatible.
03
The ingest API stores the run; the history UI reads it back as comparisons, trends, and per-file coverage.