Peak Season Flash Sale Load Testing Gate Checklist
Verify retail digital storefront resilience, third-party dependency fallbacks, and throughput capacity before major traffic spikes.
Run this checklist before Black Friday, Cyber Week, or exclusive brand drops to validate that cloud infrastructure and third-party APIs survive peak transactional surges without dropping orders.
Role: Staff Site Reliability and Performance Testing Engineer in High-Scale Retail.
Context
- Client organisation: {{retail_client_name}}
- Peak concurrency target: {{target_peak_tps}} transactions per second
- Primary shopper paths: {{critical_user_journeys}}
- Target cloud architecture: {{cloud_infrastructure_stack}}
- Downstream external dependencies: {{third_party_apis}}
- Maximum allowable p95 latency: {{maximum_acceptable_latency}}
Task
Generate a rigorous pre-event performance test gate checklist to validate that {{retail_client_name}} can sustain peak volume without database deadlocks, API throttling, or broken checkout flows.
Method
- Establish baseline synthetic load profiles mirroring {{critical_user_journeys}} up to {{target_peak_tps}}.
- Formulate stress test verification points targeting auto-scaling triggers in {{cloud_infrastructure_stack}}.
- Create mock and rate-limiting failure injection steps for external dependencies in {{third_party_apis}}.
- Define database connection pool, redis cache invalidation, and lock contention monitoring checkpoints.
- Specify performance verification checks measuring p95 and p99 against the {{maximum_acceptable_latency}} threshold.
- Detail circuit-breaker and graceful degradation validations when downstream vendors fail.
- Establish automated log and trace verification procedures to isolate silent order drops during spike phases.
Constraints
- Checklist items MUST include specific quantitative performance metrics and pass criteria.
- MUST NOT permit ambiguous pass thresholds like "system remains responsive".
- MUST validate graceful degradation behaviors for every entry in {{third_party_apis}}.
- Every section must contain actionable checkboxes formatted in markdown (
- [ ]).
Output format
Return the output in formatted markdown with the following sections:
- Load Testing Profile & Parameters (brief summary table)
- Pre-Test Environment Preparation & Data Seeding Checklist (4-6 items)
- Spike & Sustained Load Execution Gate (6-8 items)
- Third-Party Fault Injection & Circuit-Breaker Checklist (4-6 items)
- Post-Test System Recovery & Data Consistency Checklist (4-5 items)
- Final Go/No-Go Approval Matrix (compact markdown table)
Self-review
- Verify that {{target_peak_tps}} and {{maximum_acceptable_latency}} are directly utilized in the threshold definitions.
- Check that fault injection coverage spans all systems listed in {{third_party_apis}}.
- Ensure each checklist item is clear, binary, and leaves no room for subjective interpretation.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.