QA Tester Role in Retail What the Job Really Looks Like

Offer: Buy 2 get 1 free on items of the same category

TC01  Add 3 eligible items -> cheapest one free
TC02  Add 2 eligible items -> no discount
TC03  Add 4 eligible items -> one item free (not two)
TC04  Add 6 eligible items -> two items free
TC05  Mix eligible + non-eligible -> only eligible counted
TC06  Remove one item after offer applied -> recalculated
TC07  Offer expired at midnight -> not applied after expiry
TC08  Offer + coupon together -> follows stacking rule
TC09  Return one free item -> refund rules applied correctly

POS billing checks (each release)

[ ] Scan by barcode and by manual code
[ ] Quantity change and item void
[ ] Tax calculated per item category
[ ] Rounding on the final amount
[ ] Split payment (card + cash / UPI)
[ ] Receipt shows items, tax, discounts, total
[ ] Bill reprint and cancellation with manager approval
[ ] Offline mode: bills sync when network returns

Yesterday:
- Tested new 'Weekend Combo' offer: 18/20 cases passed
- Logged BUG-2210: combo discount applied twice on reload

Today:
- Retest BUG-2210 after fix
- Start testing loyalty points on online checkout

Blockers:
- Need test store data with expired loyalty points

Release 5.12 - QA summary

Scope tested: Weekend Combo offer, loyalty points,
              checkout address changes
Regression: 142 cases run, 140 passed, 2 known low issues
Open bugs: BUG-2215 (low) - receipt font misaligned
Not tested: Store printers model X (device unavailable)

Recommendation: Go, with the printer check scheduled
in one pilot store before rollout.

-- Orders marked paid but missing a successful payment record
SELECT o.order_id, o.status, o.total_amount
FROM orders o
LEFT JOIN payments p
  ON p.order_id = o.order_id AND p.status = 'SUCCESS'
WHERE o.status = 'PAID'
  AND p.order_id IS NULL;

-- Items whose website price differs from the master price list
SELECT w.sku, w.price AS web_price, m.price AS master_price
FROM web_prices w
JOIN master_prices m ON m.sku = w.sku
WHERE w.price <> m.price;

// Postman test script for GET /api/products/{sku}/price
pm.test("status is 200", () => pm.response.to.have.status(200));

pm.test("price matches expected MRP and is positive", () => {
    const body = pm.response.json();
    pm.expect(body.price).to.be.above(0);
    pm.expect(body.price).to.eql(Number(pm.environment.get("expected_price")));
});

pm.test("currency is INR", () => {
    pm.expect(pm.response.json().currency).to.eql("INR");
});

Coupon rules decision table

| Cart >= 999 | First order | Coupon valid | Discount |
|-------------|-------------|--------------|----------|
| Yes         | Yes         | Yes          | 20%      |
| Yes         | No          | Yes          | 10%      |
| No          | Yes         | Yes          | 10%      |
| No          | No          | Yes          | None     |
| Any         | Any         | No           | None     |

One test per row, plus boundaries: 998, 999, 1000.

Test the same feature across channels

Feature: Loyalty points redemption

| Channel        | Redeem | Partial redeem | Refund returns points |
|----------------|--------|----------------|-----------------------|
| Store POS      |        |                |                       |
| Website        |        |                |                       |
| Android app    |        |                |                       |
| iOS app        |        |                |                       |

Mark Pass / Fail / Not tested in each cell.

Title: [Area] [What fails] when [condition]
Example: Checkout charges full price when
         combo offer item is removed and re-added

Environment: build, channel, store ID / browser
Steps: 1. ... 2. ... 3. ...
Expected: ...
Actual: ...
Evidence: screenshot, receipt photo, API response
Impact: number of affected bills or orders if known