Testing E2E

Overview

Use this skill to validate business-critical journeys under integrated runtime conditions.

Scope Boundaries

• Use when failure risk is in end-to-end user or operator flows.
• Typical requests:
  • Validate checkout flow across UI, API, and payment integration.
  • Define minimum critical E2E regression set before release.
  • Prove no fatal breakage in top user journeys.
• Do not use when:
  • Only deterministic function logic must be tested (testing-unit).
  • Only interface compatibility is required (testing-contract).

Inputs

• Critical journey map and release risk profile
• Test environment constraints and dependencies
• Existing automation assets and known flaky areas