Back to Cookbook
KiloClaw

E2E Critical Path Suite

Keep end-to-end confidence without the unmaintainable monster

Establish a minimal set of end-to-end tests for critical journeys, backed by contract tests and targeted integration tests, to balance confidence with speed.

CommunitySubmitted by CommunityWork18 min

INGREDIENTS

🐙GitHub

PROMPT

Create a skill called "E2E Critical Path Suite". Ask me for: - The top user journeys and failure tolerance - Current test pyramid mix (unit/integration/e2e) Produce: - A critical-path E2E plan (what to keep, what to move down the pyramid) - A PR vs nightly execution strategy - Stability requirements and test data strategy

How It Works

E2E tests are expensive and can be flaky, but they catch integration failures. This recipe

defines a "critical path" subset and moves non-critical coverage down the pyramid.

Triggers

  • E2E suite is slow and brittle
  • Teams debate whether E2E is "worth it"
  • PR gating is blocked by UI test flakiness

Steps

  1. Identify top business-critical journeys (3–10 flows).
  2. Implement E2E only for those journeys, with strict stability requirements.
  3. Add contract/integration tests for service boundaries.
  4. Run E2E critical path on PR; run full E2E nightly or on-demand.
  5. Add failure triage: screenshots, traces, and reproducible fixtures.

Expected Outcome

  • Faster pipelines and higher-confidence releases.
  • Less flake-induced reruns and fewer "E2E is useless" arguments.

Example Inputs

  • "Checkout flow must never break."
  • "Login and password reset are critical."
  • "We need UI confidence but can't afford 1-hour suites."

Tips

  • Treat E2E as "integration contracts in motion," not as brute-force coverage.
Tags:#testing#flaky-tests#ci-cd#release-management