Testing
AuraScore 85/100

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.

Template

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

  1. Establish baseline synthetic load profiles mirroring {{critical_user_journeys}} up to {{target_peak_tps}}.
  2. Formulate stress test verification points targeting auto-scaling triggers in {{cloud_infrastructure_stack}}.
  3. Create mock and rate-limiting failure injection steps for external dependencies in {{third_party_apis}}.
  4. Define database connection pool, redis cache invalidation, and lock contention monitoring checkpoints.
  5. Specify performance verification checks measuring p95 and p99 against the {{maximum_acceptable_latency}} threshold.
  6. Detail circuit-breaker and graceful degradation validations when downstream vendors fail.
  7. 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:

  1. Load Testing Profile & Parameters (brief summary table)
  2. Pre-Test Environment Preparation & Data Seeding Checklist (4-6 items)
  3. Spike & Sustained Load Execution Gate (6-8 items)
  4. Third-Party Fault Injection & Circuit-Breaker Checklist (4-6 items)
  5. Post-Test System Recovery & Data Consistency Checklist (4-5 items)
  6. 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.
AuraScore breakdown
85/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification10/14 · Adequate

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-testing
retail-consumer-goods
performance-testing
load-testing
retail