Check whether the outcome improved
Exercise creation paths
Submit once, twice rapidly, after a timeout, after refresh, and after a late confirmation. Assert idempotency behavior, order identifiers, payment attempts, and confirmation result. Use synthetic fixtures and retain the request sequence for every outcome.
Exercise listing paths
Refresh, paginate, sort, filter, revisit confirmation, and load adjacent pages. Assert each identifier appears once per intended scope and that distinct orders remain separate. Check stale cache and delayed response fixtures where the harness can control them.
Compare durable records
Match rendered rows with order, payment, and fulfillment records. Verify no visual fix hides a second saved order and no safe retry creates another. Mark uncontrolled timing or external status as partial, with the missing proof recorded.
What to carry forward
Accept when controlled retries and list states produce one canonical row per order while preserving genuinely distinct records. Mark financial or fulfillment reconciliation partial if fixtures cannot prove it, and keep the owner and evidence gap attached.
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