Published by CI · commit e69b65f · 2026-09-14
The evidence, not the claim.
Every push to main runs the lab's quality gates and publishes their evidence here. The
repository README explains which layer each risk is tested at; these pages show what the last run
actually saw.
run #10
-
01
CI job ↗
Unit and API tests
Table-driven validation boundaries and in-process HTTP semantics (400 vs 500, malformed JSON, failing repository). Coverage thresholds enforced.
-
02
Report ↗
Mutation testing
Stryker injects faults into
src/and counts how many the suites catch. CI fails under 80%. Surviving mutants are highlighted in source. -
03
CI job ↗
Contract tests
The UI client's Pact is generated by the consumer test and replayed against the real Express app in the same job; the pact file is uploaded as an artifact.
-
04
CI job ↗
Integration with PostgreSQL
A disposable
postgres:16container proves the CHECK and primary-key constraints and the full HTTP-to-database path. -
05
Report ↗
Browser E2E and accessibility
The checkout journey verified through the API, two mocked failure paths, and axe-core WCAG scans before and after interaction.
-
06
Summary ↗
Performance
k6 protocol test against the lab booted inside the runner, gated on p95 and error-rate thresholds.
-
07
Spans ↗
Observability
The instrumented server is started during publishing, three requests are sent, and the exported spans are kept as evidence.
-
08
Runs ↗
AI evaluation
Promptfoo checks a fictional support assistant for valid JSON, mandatory escalation and refusal of data requests. Runs on demand with a model key.