Aglet

How to verify checkout total calculations across cart and payment

Verification must show that the review amount, payment amount, and saved order agree across the states that exposed the mismatch. Use deterministic carts and assert each component, because a matching grand total can hide an offsetting discount, tax, or shipping error.

Check whether the outcome improved

  1. Build a calculation matrix

    Cover one item, multiple quantities, fractional prices, a discount, tax, shipping, and a zero-discount case. Include the affected currency precision. Assert subtotal, adjustments, total, and the value displayed immediately before payment, not just the final number.

  2. Exercise state changes

    Run the matrix after quantity edits, refresh, back navigation, a second tab, and an idle period. Confirm recalculation replaces stale values and that a failed recalculation leaves an explicit safe state. Record the exact cart version or fixture used for each result.

  3. Compare saved outcomes

    Complete the safe test path and compare the payment summary, order fields, and confirmation display. Verify that a rejected or interrupted payment does not create a contradictory total. Keep test credentials and personal data out of screenshots and logs.

What to carry forward

Accept the change only when every tested component agrees at each boundary and the interrupted paths remain explicit. If a currency, tax, or eligibility case cannot be exercised, mark verification partial and keep that gap attached to the work record.

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