Part of: Launch · Blocked by: P13, L2–L6 · Blocks: L15
What you're building
Two deliberate breakages, to prove the safety nets work.
Why it matters
The whole three-layer pipeline design rests on a claim: when things break, users get old
prices with visible dates, never nothing and never wrong numbers.
Everyone believes it. Nobody has checked. And the scenario is exactly the one that'll happen
in two years with nobody watching.
What to do
Test 1 — every pricing site blocks us:
- Run the pipeline with every source unreachable
- Confirm it finishes without failing
- Confirm it publishes a complete catalog for all 20 devices
- Confirm every price kept its original date, not today's — this is the one that's easy
to get wrong, and getting it wrong hides the problem from users
- Confirm the app works normally and shows the older dates
Test 2 — the pipeline crashes:
- Make it fail before it builds the file
- Confirm nothing is published
- Confirm last month's catalog is still being served
- Confirm the app keeps working
- Confirm an alert fires
What not to do
- Don't skip test 1 because it seems obvious. The date behaviour is the whole point and it's
easy to get backwards.
Done when
Part of: Launch · Blocked by: P13, L2–L6 · Blocks: L15
What you're building
Two deliberate breakages, to prove the safety nets work.
Why it matters
The whole three-layer pipeline design rests on a claim: when things break, users get old
prices with visible dates, never nothing and never wrong numbers.
Everyone believes it. Nobody has checked. And the scenario is exactly the one that'll happen
in two years with nobody watching.
What to do
Test 1 — every pricing site blocks us:
to get wrong, and getting it wrong hides the problem from users
Test 2 — the pipeline crashes:
What not to do
easy to get backwards.
Done when