Promo Codes Testing Checklist (2026)

Promo Codes Testing Checklist (2026)

By · January 22, 2026 · 20 min read · Testing Checklists

Promo Codes Testing Checklist (2026)

A promo code is a short alphanumeric token that unlocks a discount, free trial, gift, or other incentive when entered during checkout or account creation. Testing promo codes thoroughly prevents revenue leakage, protects brand trust, and avoids regulatory pitfalls. The checklist below groups 38 concrete items into seven functional areas plus a release‑readiness section. Each item includes a pass criterion, a real‑world example, and notes on how manual, automated, or autonomous exploration (e.g., with SUSA) can cover it.

---

Promo Codes Testing Checklist (2026) – Happy Path

Core redemption flow

#Test ItemPass CriterionExampleAutomation Hint
1Valid code entry on checkout pageDiscount applied correctly, order total reflects new amount, confirmation shows code usedCode “SPRING20” gives 20 % off a $100 cart → $80 totalUI test enters code, asserts price change
2Code applied before paymentDiscount visible on cart summary before proceeding to paymentUser sees “- $20” line item after code entryAssert DOM element text before “Pay” button click
3Code works on first‑time userNew account receives discount, no prior purchase requiredGuest checkout with code “WELCOME10” → 10 % offCreate fresh test user, run flow
4Code works for returning userExisting logged‑in user can redeem without re‑authenticationLogged‑in user applies “LOYALTY15” → discount appliedUse session cookie or login API
5Code works across devicesSame code yields identical discount on mobile web, native app, and desktopCode “BLACKFRIDAY” works on iOS app, Android web, ChromeRun matrix of device/OS combos
6Code works with multiple itemsDiscount applies to cart total, not per‑item unless specifiedCart with 3 items ($30 each) → 10 % off total $90 → $81Assert total after code entry
7Code works with shipping taxesDiscount calculated before tax/shipping or after, per business ruleIf discount pre‑tax: $100 + $10 tax → 20 % off $100 = $80 + $10 tax = $90Verify tax line matches rule
8Code works with gift cardsGift‑card balance + promo discount both applied$50 gift card + “SAVE5” → $5 off → final $45 chargeCheck both balances updated
9Code works with subscription plansRecurring discount applied to first billing cycleCode “FIRSTMONTHFREE” → $0 first month, then regular priceVerify subscription object shows discount flag
10Code works with bundled offersBundle discount stacks or does not stack per policyBundle “BOXSET” 15 % off + code “EXTRA10” → either 23.5 % stacked or 15 % onlyValidate against promo‑stacking rule

Success messaging & receipt

#Test ItemPass CriterionExampleAutomation Hint
11Success toast/message appearsNon‑blocking toast with code name and discount amount displayed for ≥2 s“SPRING20 applied – saved $20”Wait for toast element, assert text
12Order confirmation email includes codeEmail body lists redeemed promo and discounted amount“Promo: SPRING20 – Discount: $20.00”Parse email fixture, assert substring
13Order history shows promo usageUser’s order detail page shows promo code field populatedOrder #12345 → Promo: WELCOME10API GET /orders/{id} assert promo field
14Loyalty points adjusted (if applicable)Points earned reflect discounted spend, not originalSpend $80 after 20 % off → earn 8 points (10 pts/$)Check points balance after order
15Referral credit not double‑countedIf promo and referral both apply, each credited onceReferral gives $5, promo gives 10 % → total correctVerify both credits in ledger

---

Promo Codes Testing Checklist (2026) – Error Handling

Invalid code detection

#Test ItemPass CriterionExampleAutomation Hint
16Non‑existent codeError message “Invalid promo code” displayed, no discount appliedEnter “FAKE123” → toast: “Code not found”Assert error element visible, price unchanged
17Expired codeMessage “This promo has expired”Enter “SUMMER21” after 30 Sep 2021 → errorSet system date or use backend flag
18Code used beyond usage limitMessage “This promo has reached its usage limit”Code limited to 100 uses, 101st entry failsPre‑populate usage counter via API
19Code not applicable to cart itemsMessage “Promo not valid for selected items”Code for “Shoes only”, cart contains a shirtVerify error, discount not applied
20Code requires minimum spendMessage “Spend $50 to use this promo”Cart $30 + code “SAVE10” → errorTest cart just below and just above threshold
21Code restricted to user segmentMessage “This promo is for new users only”Existing user tries “NEWUSER20” → errorAttach user‑type flag, assert denial
22Code case‑sensitivity handlingSystem treats code as case‑insensitive (or as defined)If case‑insensitive, “spring20” works; if strict, failsTry both variations
23Code with special charactersAccepts hyphen, underscore, or rejects per spec“SPRING-20” accepted; “SPRING@20” rejected if not allowedSend varied strings, check response
24Leading/trailing whitespaceSystem trims whitespace before validationEnter “ SPRING20 ” → acceptedSend code with spaces, assert success
25Code length limitsRejects codes shorter than min length or longer than maxMin 5, max 12 → “ABCD” rejected, “ABCDEFGHIJKL” rejectedBoundary test with 4,5,12,13 chars
26Duplicate submission preventionSecond submit of same code shows “already applied” not errorAfter first apply, clicking Apply again → toast “Code already used”Click button twice, verify state
27Network timeout fallbackUI shows retry option, does not apply discount twiceSimulate 5 s delay on /apply endpoint → show retryMock server delay, assert UI behavior
28Server error (5xx) handlingShows generic “Try again later”, does not consume codeReturn 500 on apply → error toast, code still validMock 500, verify code not marked used
29Client‑side validation bypassEven if JS disabled, server rejects invalid codeDisable JS, submit “BADCODE” → server errorUse curl or fetch without JS, assert 400
30Race condition under high loadConcurrent requests for same limited‑use code grant discount to only one user10 users submit same code simultaneously → only 1 succeedsUse k6 or Locust to fire parallel requests, check counts

---

Promo Codes Testing Checklist (2026) – Edge / Boundary Cases

Discount calculations

#Test ItemPass CriterionExampleAutomation Hint
31Percentage >100%System rejects or caps at 100 % (per policy)Code “FREE200” → error or free itemTry 150 % code, assert rejection or zero price
32Fixed amount > cart totalDiscount cannot make total negative; total set to $0Cart $5, code “TAKE10” → $0 total, not –$5Assert max(0, total‑discount)
33Fractional cents handlingRounding follows bankers’ rounding or defined rule$49.99 with 33 % off → $33.4935 → $33.49 or $33.50Compute expected, assert exact cents
34Multiple percentage stacksIf stacking allowed, apply sequentially not additively10 % then 10 % on $100 → $81, not $80Apply two codes, verify final
35Tiered discount thresholdsDifferent % based on spend brackets$0‑$49 → 5 %; $50‑$99 → 10 %; $100+ → 15 %Test cart values at each boundary
36Time‑zone sensitivityPromo active based on UTC start/end, not localCode active 00:00 UTC Jan 1 – 23:59 UTC Jan 31Set device TZ, verify activation/inactivation
37Daylight‑saving shiftNo double‑count or skip when clocks changePromo runs 01:00‑03:00 local, DSB shift → still 2 h windowSimulate clock change, check active period
38Leap year February 29Promo scheduled for Feb 29 works only on leap yearsCode “LEAP2024” active Feb 29 2024, not 2025Set date to 2024‑02‑29, assert active; 2025‑02‑28 assert inactive

Input & UI edge cases

#Test ItemPass CriterionExampleAutomation Hint
39Max length fieldInput field accepts up to defined max, blocks extraField max 12 → typing 13th char blocked or trimmedSend long string, assert length
40Paste from clipboardPasted code validated same as typedPaste “SPRING20” → worksUse clipboard API in test
41Autocomplete suggestionsNo suggestion reveals inactive or expired codesTyping “SPR” shows only active codesObserve dropdown, assert no expired
42Right‑to‑left language layoutField aligns correctly, cursor moves as expectedArabic UI: code entry right‑alignedSwitch locale, inspect direction
43Zoom level 200%All elements readable, no overlapPromo entry visible at 200% zoomSet browser zoom, assert no overflow
44Screen orientation changeState preserved on rotateEnter code, rotate to landscape → code still shownRotate device/emulator, assert field value
45Hardware keyboard vs on‑keyboardBoth produce same resultDesktop keyboard entry works, mobile OSK worksTest both input methods
46Voice input transcriptionVoice‑to‑text yields correct codeSay “spring two zero” → “SPRING20”Use speech API, verify result
47Barcode/QR code scanScanned code populates field and validatesScan QR encoding “SPRING20” → field filledUse camera mock, assert success
48Copy‑protected fieldRight‑click copy disabled if requiredAttempt to copy code from tooltip → blockedTry document.execCommand('copy'), expect failure
49Invalid Unicode normalizationDifferent visual forms treated same“SPRING20” with full‑width chars → acceptedSend full‑width variants, assert same outcome
50Emoji injectionEmoji ignored or causes validation errorEnter “SPRING20😀” → rejectedSend emoji, assert error

---

Promo Codes Testing Checklist (2026) – Accessibility

#Test ItemPass CriterionExampleAutomation Hint
51Label associationEach input has associated <label> or aria-label<label for="promo">Promo code</label>axe-core asserts label present
52Keyboard navigableTab moves focus to code field, Apply button, then nextTab order: field → button → continueSimulate Tab key, check focus order
53Visible focus indicatorField shows outline ≥2 px when focusedCSS outline: 2px solid #005fccCheck computed style on focus
54Error message ARIA liveInvalid code triggers aria-live="assertive" region<div aria-live="assertive" id="promo-error">Assert live region updates on error
55Contrast ratioText and background meet WCAG AA (≥4.5:1)Promo text #212529 on #fff → 7.5:1Use axe or manual contrast tool
56Scalable textUp to 200% text size does not break layoutIncrease browser font size → field still usableSet font-size: 200%, assert no overflow
57Screen reader announces discountAfter successful apply, reader says “Promo SPRING20 applied, saved $20”Use NVDA or TalkBack to verifyRecord utterance, assert phrase
58Touch target sizeApply button ≥44 dp × 44 dpButton dimensions 48 × 48 dpMeasure via UIAutomator or Espresso
59Reduced motion respectedAnimation disabled if prefers-reduced-motionNo fade/tooltip slide when setting enabledCheck CSS media query, assert no animation
60High contrast modeColors invert or adapt correctlyIn Windows HC mode, promo field uses system colorsEnable HC, assert readable contrast
61Language switch preserves stateChanging language does not clear entered codeEnter code, switch to French → code still presentChange lang attribute, assert field value
62Error announcement timingError announced within 400 ms of invalid entryLive region triggers promptlyMeasure time between input and screen reader output
63Focus returned after modalAfter promo‑info modal closes, focus returns to fieldClose “How promo works” dialog → focus on fieldTrigger modal, close, assert activeElement
64No placeholder as sole labelPlaceholder not used as only label (fails WCAG)Field has both placeholder and visible labelInspect DOM, fail if only placeholder
65Accessible name for icon-only buttonApply button with icon has aria-label="Apply promo"Icon button <button aria-label="Apply promo">Assert aria-label present
66Skip link to promo fieldEarly skip link jumps directly to promo entry<a href="#promo-field">Skip to promo</a>Activate link, assert focus on field
67Responsive breakpoint accessibilityLayout does not hide promo field on small screens@media (max-width:320px) field still visibleResize viewport, assert field present
68No autoplay audio on promo pagePage does not play sound automaticallyNo <audio autoplay>Scan DOM for audio elements without user gesture
69Error message announced in user languageIf UI language is Spanish, error appears in Spanish“Código no válido”Change locale, assert translated message
70Focus trap in modalWhen promo‑info modal opens, tab does not escapeTab cycles within modal until closedOpen modal, press Tab repeatedly, assert focus stays inside

---

Promo Codes Testing Checklist (2026) – Security & Privacy

#Test ItemPass CriterionExampleAutomation Hint
71Code leakage in URLPromo code never appears in query string or fragmenthttps://shop.example/cart?promo=SPRING20 → forbiddenInspect network calls, assert no promo in URL
72Code masked in logsBackend logs replace promo with <strong>*</strong>Log line: Applied promo: ****Check log samples, assert masking
73Rate limiting on apply endpointMax N requests per IP/minute to prevent brute force10 requests/min → 11th returns 429Use curl loop, assert 429 after limit
74JWT/session bindingPromo apply requires valid authenticated sessionAnonymous POST to /apply returns 401Send request without cookie, assert 401
75Code entropy checkSystem rejects predictable sequences (e.g., “111111”)“111111” → error “code too weak”Try weak patterns, assert rejection
76No SQL injection via promo fieldInput sanitized, injection attempt fails' OR 1=1-- → error, no DB errorSend payload, assert no 500, DB unchanged
77No XSS via promo displayRendered code escaped, no script execution<script>alert(1)</script> rendered as textInject script, assert not executed in DOM
78CSP blocks inline scriptContent‑Security‑Policy prevents inline JS from promo UIscript-src 'self' blocks attemptsVerify CSP header, try to inject <script>
79Rate limit per code per userSame user cannot apply same code more than allowed limitUser tries apply 5 times → after 1st, further attempts blockedLoop apply, assert 403/429 after first
80Audit log captureEach apply/create/delete logged with user ID, timestamp, IPLog entry: user_id=42, promo=SPRING20, action=applyQuery audit table, assert fields
81GDPR right to erasureDeleting user account removes associated promo usage recordsAfter delete, query shows no promo usage for that userDelete user, assert no rows in promo_usage
82Data minimizationOnly necessary promo metadata stored (code, discount, validity)No storage of full cart contents with promoInspect DB schema, assert minimal columns
83Secure transmissionAll promo‑related API calls use HTTPS with TLS 1.2+https://api.example/promo/apply TLS 1.3Use Wireshark or sslyze to confirm
84Code expiration enforcement server-sideEven if client tampers with date, server rejects expiredSet client date to past, send expired code → server 400Mock client time, assert server rejection
85Promo code regeneration after breachIf a code is leaked, system can invalidate and issue newAdmin revokes “LEAKED123”, issues “LEAKED123v2”Call revoke API, verify old code fails, new works
86No promo code in error messagesError does not reveal whether code exists or notGeneric “Invalid promo” not “Code SPRING20 not found”Test with valid vs invalid, compare messages
87Rate limit exemption for internal toolsInternal admin tools have higher limits, but still loggedAdmin can bulk‑load 1000 codes/minTest with admin token, assert allowed, logged
88Promo code cannot be guessed via sequential enumerationPredictable pattern (e.g., SPRING01‑SPRING99) not all validOnly some in range active, others invalidBrute‑force range, assert only expected succeed
89Secure random generationCodes generated using CSPRNG, not simple rand()Distribution uniform over 62^8 spaceSample 10k codes, chi‑square test for uniformity
90Expiration stored as UTC timestampAvoids ambiguity across time zonesDB column expires_at TIMESTAMP WITH TIME ZONEVerify column type, assert UTC storage

---

Promo Codes Testing Checklist (2026) – Performance

#Test ItemPass CriterionExampleAutomation Hint
91Apply latency < 300 ms (p95)95 % of promo apply calls return within 300 ms under normal loadMeasure with k6, assert p95 ≤300msRun load test, extract percentile
92Throughput ≥ 500 applies/secSystem sustains at least 500 successful apply requests per secondLoad test with 500 VUs, 2 sec rampCheck requests/sec metric
93Cache hit ratio ≥ 80 % for valid codesFrequently used codes served from Redis/MemcachedAfter warm‑up, 8 out of 10 reads hit cacheInspect cache stats, assert ratio
94No memory leak during repeated appliesHeap growth < 5 MB after 100k apply cyclesRun loop, monitor process memoryUse pmem or valgrind, assert bound
95Database lock contention minimalAverage lock wait time < 10 ms under 200 VUCheck DB pg_locks or innodb_lock_waitQuery pg_stat_activity, assert low wait
96Async discount calculation non‑blockingUI does not freeze while calculating complex tiered discountMeasure main thread JS idle timeUse Chrome DevTools Performance, assert < 50ms block
97Bulk promo upload endpoint ≤ 2 s per 1k codesAdmin can upload 1k codes in ≤2 secondsPOST /promo/bulk with 1k JSON objectsTime request, assert ≤2000ms
98Graceful degradation under high latencyIf promo service slow, UI shows “Applying…” spinner, not blankSimulate 2 s delay, assert spinner visibleMock latency, assert UI state
99Rate limit headers presentResponse includes X-RateLimit-Limit, X-RateLimit-RemainingHeader: X-RateLimit-Limit: 60Check response headers
100Payload size ≤ 2 KB for apply requestJSON body small to save bandwidth{ "promo": "SPRING20" } ≈ 22 bytesMeasure request size, assert < 2048
101Promo validation does not trigger full cart recompute unnecessarilyOnly affected line items recalculatedIf promo applies to shipping only, cart, say, items with tag “electronics”, only those items recomputedInstrument backend, assert limited recompute calls
102Discount calculation uses fixed‑point arithmeticAvoid floating‑point rounding errors in high volumeUse Decimal or integer centsInspect codebase for float usage, assert absent
103Promo service scales horizontallyAdding another instance does not change latencyDeploy 2 vs 3 replicas, compare p95 latencyRun same load on different replica counts
104HTTP/2 or QUIC used for promo callsMultiplexing reduces connection overheadObserve protocol in Chrome devtools NetworkAssert h2 or h3 in protocol column
105Promo-related third‑party calls (e.g., fraud check) have timeout ≤ 500 msPrevents hanging UISet stub to delay 600 ms → UI shows timeout fallbackMock external service, assert fallback shown
106Load test with mixed valid/invalid codes mimics real traffic80 % valid, 20 % invalid reflects production ratioRun test with 80/20 mix, ensure error handling does not degrade valid pathMix request types, assert valid latency unaffected
107Auto‑scale trigger based on promo apply latencyScale‑out if p95 latency > 250 ms for 2 minSet CloudWatch alarm, verify new instance addedSimulate latency spike, observe autoscaling event
108Promo API idempotentRetrying same request with same idempotency key yields same result, no double discountSend same request twice with Idempotency-Key: abc → second returns 200 with same discount, no extra deductionUse idempotency header, assert balance unchanged after retry
109Discount application does not cause database deadlock under concurrencyNo deadlock errors when 100 users try to apply same limited‑use codeRun concurrent script, check DB logs for deadlockAssert zero deadlock occurrences
110Promo usage analytics pipeline keeps up with peakEvents flushed to Kafka/Warehouse within 2 s of applyMeasure lag from apply event to consumptionAssert lag < 2000ms

---

Promo Codes Testing Checklist (2026) – Release Readiness

#Test ItemPass CriterionExampleAutomation Hint
111Feature flag togglePromo system can be disabled via flag without breaking checkoutFlip flag promo_enabled=false → checkout works, promo UI hiddenToggle flag, assert promo fields absent
112Rollback script validatedDB migration to add promo tables includes down‑script that removes them safelyRun migrate up, then down → schema same as pre‑migExecute migration scripts in test DB
113Canary release monitoring5 % traffic routed to new promo version, error rate < 0.1 %Deploy canary, watch SLO dashboardAssert error rate stays below threshold
114A/B test framework integrationPromo variations can be toggled per experiment IDExperiment promo_discount_ab serves 10 % vs 15 %Check experiment service returns correct variant
115Documentation updatedRelease notes include new promo fields, validation rules, and deprecationsChangelog entry: “Added max_uses_per_user field”Search docs for keyword, assert present
116Training for support teamSupport has FAQ covering common promo issues (expired, usage limit)FAQ article “Why is my promo not accepted?” existsVerify internal knowledge base contains article
117Monitoring alerts configuredAlert on promo apply failure rate > 2 % or latency > 400 msPrometheus rule: rate(promo_apply_errors[5m]) > 0.02Check alertmanager config, assert rule present
118Load test sign‑offPerformance test results signed off by performance engineerDocument: “Promo apply p95 latency 210 ms @ 800 VU”Locate sign‑off artifact, assert present
119Security review completedNo open high‑severity findings in promo code handlingSAST/DAST report shows 0 criticalRetrieve report, assert severity count
120Accessibility audit passedAxe score ≥ 90 % on promo pageRun axe-cli, assert score ≥ 90Execute audit, capture score
121Feature toggle for promo‑experimentsAbility to turn off experimental promo types without redeployFlag promo_exp_enabled=false hides beta UIToggle flag, assert experimental variants hidden
122Deprecation notice for old promo formatIf migrating from legacy alphanumeric to UUID‑based codes, notice shownBanner: “Old promo format will be disabled 2026‑07‑01”Check UI for banner when legacy code present
123Rollback test in stagingFull end‑to‑end rollback of promo feature does not leave orphan dataDeploy rollback, run smoke test → no promo tables, no promo usage rowsExecute rollback, query DB for leftover rows
124Customer‑facing communication preparedEmail/template ready to announce new promo types to usersDraft email: “Introducing SPRING20 – 20 % off sitewide”Locate template, assert placeholders filled
125Support runbook for promo incidentsRunbook includes steps to investigate promo‑apply failures, clear cache, check DB locksRunbook doc ID: RUN-PROMO-01Verify runbook exists, contains required sections
126Logging correlation ID presentEach promo request carries a trace ID linking frontend, backend, analyticsHeader X-Trace-ID: a1b2c3d4Inspect request/response headers, assert ID present
127Backwards compatibility for older clientsClients on API v1 still able to apply promos via legacy endpoint/v1/promo/apply returns same shape as /v2/promo/applyCall v1 endpoint, assert response fields match v2
128Database indexes on promo columns adequateIndex on (code, active) ensures fast lookupsExplain query shows index usageRun EXPLAIN on select, assert index used
129Promo service health endpoint returns 200 with JSON {status:"OK"}/health/promo responds quicklyGET /health/promo → {status:"OK"} in < 50 msCall endpoint, assert body and latency
130Feature flag for promo‑specific experiments (e.g., stacked discounts)Ability to enable/disable stacking per experiment without code changeFlag promo_allow_stacking=true/falseToggle flag, assert stacking behavior changes

---

How Autonomous Exploration Covers Most of This Checklist in One Pass

SUSA (SUSATest) is an autonomous QA agent that, given an APK or a web URL, explores the application like a combination of curious, impatient, novice, power‑user, and adversarial personas. It automatically generates UI interactions, API calls, and validation checks without hand‑written test scripts. When pointed at an e‑commerce flow that includes promo code entry, SUSA can satisfy a large subset of the checklist above:

Checklist AreaItems Covered by SUSA (examples)How SUSA Achieves It
Happy Path1‑10, 11‑15 (code entry, discount verification, messaging, email, loyalty)SUSA’s “curious” persona tries every visible input, submits forms, reads toast messages, extracts order totals from the DOM, and can even sniff outbound emails via a test mailbox to validate confirmation content.
Error Handling16‑30 (invalid, expired, usage‑limit, segment restrictions, whitespace, duplicate submission, network faults)The “adversarial” persona deliberately submits malformed data, expired codes (by manipulating system clock via environment variable), and repeats actions. SUSA also injects latency using network throttling plugins to provoke time‑outs and retries.
Edge/Boundary31‑38 (percentage caps, rounding, time‑zone, leap year, stacking)By varying cart totals, applying multiple codes, and adjusting device time‑zone settings, SUSA’s “power‑user” persona explores edge arithmetic and temporal boundaries.
Accessibility51‑70 (labels, focus, ARIA live, contrast, screen‑reader announcements, touch targets)SUSA runs axe‑core in the background on each page load, captures contrast failures, and uses accessibility APIs (e.g., UIAutomator on Android, AccessibilityTree on Chrome) to verify focus order, live region updates, and touch target sizes.
Security/Privacy71‑90 (URL leakage, logging masking, rate limits, injection, CSP, audit logs)SUSA’s “novice” and “impatient” personas attempt common injection strings, inspect network logs for promos in URLs, and check response headers for security flags. It also hits the apply endpoint in a loop to trigger rate‑limit responses and validates that error messages do not leak existence info.
Performance91‑110 (latency, throughput, cache hit, memory leaks, scaling, idempotency)By continuously driving the promo apply endpoint with varying load patterns (using its built‑in load‑generator), SUSA measures response times, tracks cache‑hit ratios via internal metrics, and watches for memory growth via process introspection. It also checks idempotency by resending the same request with a supplied idempotency key.
Release Readiness111‑130 (feature flags, migration scripts, canary monitoring, documentation, alerts)While SUSA does not write release notes, it can verify that a feature flag truly hides/shows the promo UI, that migration scripts are reversible (by applying then rolling back in a test DB), and that health endpoints return expected payloads. It can also confirm that alerts fire when it deliberately induces error spikes.

What SUSA does not replace

Test Your App Autonomously

Upload your APK or URL. SUSA explores like 11 real users — finds bugs, accessibility violations, and security issues. No scripts. New to the category? Start with what autonomous product intelligence & QA means.

Try SUSA Free