+232 KiB
Loading image diff...
+202
−0
Loading
Two-tier slide showing the test harness that guards every refactor.
Top half: pipeline diagram.
reference fixtures (1) →
├─ Path A: drive GUI via pytest-qt, capture .dat
└─ Path B: invoke ReductionProcess.reduce(), capture .dat
→ compare Q/R/dR/dQ + sample-log checksum (2)
→ PASS (equivalent) or FAIL (divergence with plot + JSON delta)
Bottom half: three panels showing how the harness pays off across
the hack-a-thon timeline.
- Before (Day 1): baseline measurement. Expect failures on every
fixture — each failure quantifies an active slide-3 tension,
producing a debt manifest for Day-4 EWM tickets.
- During (Days 2–5): every PR gated by the harness. Each refactor
(build_mrr_kwargs, _as_ints unification, QuickNXS scale, etc.)
turns more fixtures green. "Done" means bit-for-bit equivalent
OR explicitly sign-off-divergent reductions.
- After (permanent): CI gate forever. Would have caught commit
9e67585 (NX vs NY pixel clipping) and 2029db1 (stitching
overwrites run number) the day they landed.
Builds on existing pytest-qt / pytest-xvfb / LFS infrastructure;
no new CI resources required.
This is item 10 on slide 7 — the Tier-2 investment that makes every
other refactor safe.
Co-Authored-By:
Claude Opus 4.7 (1M context) <noreply@anthropic.com>