2026-01-12 · Software Testing

Why we deleted half our E2E suite

A postmortem on trading breadth for speed, and what we wrote back in.

Introduction

Two hundred Cypress specs gave coverage on paper and forty-minute runs in practice. We kept the journeys that protect revenue, moved the rest down the pyramid, and set a rule to keep the suite from growing back.

The mental model

  • Start from the smallest version that could work, and make it observable.
  • Write down the trade-off you are accepting, not only the feature you are shipping.
  • Revisit the decision when the team grows; most choices in Software Testing have a shelf life.

A practical starting point

  1. Reproduce the situation on a scratch branch, next to a measurement you trust.
  2. Change one variable at a time, and keep the diff small enough to explain in one sentence.
  3. Keep the result, throw away the scaffolding.
Terminal window
git switch -c experiment/one-thing

Closing thoughts

None of this is doctrine. Treat it as a checklist you are allowed to disagree with — ideally with an experiment of your own that settles the argument.