testing-e2e-flow

Key user flows Systems/services involved in the chain Environment and access Test data strategy (create/cleanup) Data and fixtures Scenario criticality </input_requirements> The scenario covers the full user path Integration points and dependencies are explicitly stated Scenarios are independent and can run in any order External service failures and timeouts are considered Steps are reproducible and deterministic Minimum number of scenarios for maximum value Test data lifecycle is defined </design_rules> Record results at each key stage Separate infrastructure failures from application logic failures Verify idempotency of critical operations Record service versions/feature flags and environment configuration Manage test data (create/cleanup) Collect logs from all involved services Record timing for key steps and failure reasons </execution_rules> Critical user flows Integration points and external dependencies Errors and resilience Data consistency Critical NFRs (response time, stability) Do not run e2e on an unstable environment Do not mix multiple business processes in one scenario Do not rely on random data Do not leave test data without cleanup </do_not> Registration -> confirmation -> checkout -> payment -> notification Create entity -> verify in report -> export data </example_flows>