jeremylongworth-source E2E Test Plan
Core Workflow
- Identify the critical user journey, entry point, data setup, success signal, and release risk.
- Choose the smallest E2E path that verifies the user-visible outcome.
- Define setup, actions, assertions, cleanup, test data, and environment.
- Include accessibility, responsive, auth, payment, email, or external-system concerns only when relevant to the journey.
- Separate smoke tests from full regression flows.
- Specify command, CI cadence, flake risks, and manual fallback.
Safety Rules
- Do not use real payment methods, production accounts, or customer data.
- Do not overuse E2E tests for behavior better covered by unit or integration tests.
- Do not claim browser flows work without runtime evidence.
Deliverable Shape
For E2E plans, provide:
- Journey and success criteria
- Environment and test data
- Steps and assertions
- Smoke versus regression scope
- Cleanup
- Command and CI cadence
- Flake risks and mitigations
References
- Read
references/e2e-test-plan-checklist.mdwhen planning E2E coverage.