Aglet

How to verify checkout currency display fixes

Verification should prove that the shopper sees one explicit currency and amount from cart through order, with formatting appropriate to the locale. Use fixed minor-unit fixtures, assert currency codes beside symbols, and test preference changes so a stale display cannot survive a new amount.

Check whether the outcome improved

  1. Build a currency matrix

    Cover integer and fractional amounts, zero, discounts, tax, shipping, currencies with different decimal precision, and representative locales. Assert numeric minor units, formatted amount, ISO code, decimal separator, and rounding rule at each checkout surface.

  2. Exercise preference changes

    Change locale, country, currency preference, quantity, and cart contents after rendering a total. Refresh and revisit payment. Confirm the displayed currency and amount update together and that an unavailable conversion stops with an explicit next action.

  3. Compare saved outcomes

    Complete safe fixtures and compare cart, payment, confirmation, order, and receipt-facing values. Verify currency code and amount persist together. Keep conversion inputs synthetic and mark any charged-currency evidence unavailable in the test harness as partial.

What to carry forward

Accept when every tested surface carries the same explicit currency and reconciled amount through preference changes and persistence. Mark unsupported precision, conversion timing, or charged-currency cases partial with the exact evidence gap and owner across supported locales.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow