Check whether the outcome improved
Define observable states
Create fixtures for immediate success, delayed order, delayed payment result, declined payment, and unresolved status. Assert the message, retry control, status lookup, order identifier, and final state. Record elapsed time as observed test data, not a promised universal threshold.
Exercise navigation
Refresh, use back and forward, close and reopen the page, and submit again after a delay. Confirm the same order remains addressable and the UI does not create a second action path. Check both desktop and narrow layouts for readable recovery copy.
Compare records
Match the confirmation, payment, order, and any follow-up state for each fixture. Verify sensitive identifiers are handled safely. Mark asynchronous paths partial when the test harness cannot control their timing, and preserve that limitation in the result.
What to carry forward
Accept when every tested path exposes one truthful state and safe next action, including delayed completion and navigation recovery. If timing cannot be controlled, report the exact unverified boundary and retain a follow-up owner instead of marking the fix fully proven.
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