Coverage Trend
How the automated-test surface grew across the parallel-build waves (Foundation → Wave H). Each bar is the net new tests a wave shipped; the spark traces the running cumulative count. Illustrative project-tracking state — the cockpit's picture of itself, not product data.
421
Tests today
+421
Added since baseline
9
Waves recorded
+72
Peak wave (G)
Cumulative tests
Running total of automated tests after each wave landed, left → right.
Tests added per wave
Net new tests each wave shipped. Bar length tracks the wave against the busiest test-writing burst; color reads as a heat scale.
Breakdown
Wave-by-wave: net new tests and the cumulative surface after each landed.
| Wave | Added | Cumulative |
|---|---|---|
| FFoundation | +12 | 12 |
| AWave A — validation-engine + ui kit | +38 | 50 |
| BWave B — web app + BE migrations | +64 | 114 |
| CWave C — write-path APIs + UX | +47 | 161 |
| DWave D — cockpit live-data + drift + E2E | +53 | 214 |
| EWave E — MVP02 backend depth | +41 | 255 |
| F2Wave F — frontend completeness | +36 | 291 |
| GWave G — i18n/auth + quality | +72 | 363 |
| HWave H — security (RLS) + E2E + design | +58 | 421 |
Test counts are the cockpit's own build log (illustrative project-tracking state), not product data. Cumulative values are running totals after each wave; an empty trend renders a safe placeholder.