Build a useful investigation brief
Reconstruct normalization
Compare raw test fields with normalized street, unit, region, and postal values. Check capitalization, punctuation, abbreviations, and country-specific field mapping. Note whether the normalized response drops information or changes a value that later rules need.
Follow dependent calculations
Use the normalized address to request shipping and tax states. Compare a passing neighboring address and record which input differs. Capture response status, validation messages, and timing. A shipping or tax rejection may be downstream of normalization rather than its origin.
Inspect persistence and resume
Interrupt after validation, return to the address step, and reload the cart. Check whether entered and normalized fields are stored consistently. Verify the order record uses the same approved address and that a failed attempt does not leave a partial destination behind.
What to carry forward
The brief is reproducible when another engineer can supply the same field shape and see the same normalization or dependent calculation difference. Include raw-to-normalized comparisons, response timing, persistence behavior, and unresolved rule ownership before recommending a change.
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