E2E Test

Overview

An end-to-end test verifies that a complete user-facing flow works correctly through the full stack. Nothing is mocked. The test interacts with the system the same way a real user or client would and asserts on observable outcomes.

Required background: Apply auto-test universal principles first. This skill adds e2e-scope specifics.

When to Use

• Testing a full user journey: login → action → outcome
• Verifying that frontend, API, and database integrate correctly end to end
• Smoke testing a deployment before promoting to production
• Regression-testing critical user paths

Not for: logic that can be verified at the unit or integration level — e2e tests are expensive; reserve them for flows that cannot be confidently verified at a lower level.

Core Principles