AI Prompt (E2E level)
Prompt text
“Outline
E2E test flows for user goal \[describe]. Include start state,
navigation steps, data setup/cleanup, cross-browser/device considerations, and
success/failure assertions.”
How to apply critical thinking
·
Think in user journeys, not screens
·
What
represents a complete success for this goal from the user’s point
of view?
·
What
critical checkpoints must be
true across multiple systems?
·
Generate E2E flows
·
Primary journey: start → navigate → perform actions → see
confirmation.
·
Alternative flows: different entry points (deep links,
notifications).
·
Failure flows: invalid input, backend failure, partial completion,
recovery.
·
Cross-system checks: UI, API, DB, emails/notifications, logs.
·
Questions on ambiguities
·
Which parts are okay to
mock vs must be real?
·
What’s the
acceptable flakiness
risk vs coverage (how many browsers/regions)?
·
Which 2–3
E2E flows are truly business-critical?
·
What test ideas might be missed
·
Long-running flows (multi-session,
multi-day tasks).
·
E2E behavior across releases (backwards compatibility).
·
User
switching devices mid-flow.
Output template (E2E
testing)
Context: [user goal, e.g., "complete checkout with discount"], systems involved
Assumptions: [data seeding approach, real vs mocked dependencies, browsers/devices]
Test Types: [E2E, regression]
Test Cases:
ID: [TC-E2E-001]
Type: [E2E]
Title: [e.g., "User completes checkout with valid card"]
Preconditions/Setup:
- [User account state, inventory, promo codes]
- [Email/SMS delivery system configured]
Steps:
1. [User logs in/registers]
2. [Adds item to cart]
3. [Applies promo]
4. [Completes payment]
5. [Views confirmation page/email]
Variations:
- [Different payment methods, shipping options]
- [Abandoned cart then resume]
- [Failed payment then retry]
- [Different browser/device combos]
Expected Results:
- [UI confirmations, order in DB, payment captured, notifications sent]
Cleanup:
- [Cancel/refund orders, restock inventory, clean test data]
Coverage notes:
- [Critical path coverage, dependencies involved, known gaps and reasons]
Non-functionals:
- [Latency of end-to-end flow, robustness under typical load]
Data/fixtures:
- [Seed scripts, test accounts, cards, promo codes]
Environments:
- [Staging/prod-parity with all integrated services]
Ambiguity Questions:
- [What is in-scope E2E vs already covered by integration tests?]
Potential Missed Ideas:
- [Cross-region flows, multi-tenant behavior, rollback/compensation flows]