Start with a reproducible failure
When an external API is slow, the interface needs an honest fallback. An old response must not restore the wrong choice merely because it arrived last.
Use a small controlled test to separate a symptom from its cause. Record the starting state, affected URL and observed outcome so that another person can repeat the check.
Collect evidence before changing anything
Delay choice A and let B respond first in the test environment. Verify that late A does not replace B. Repeat after a timeout, abandoned navigation and another attempt.
Fictional example: A visitor switches from region A to B. B shows the right contact route, but A’s slower response arrives later and restores the wrong region.
| Check | Expected outcome |
|---|---|
| Starting condition | The response belongs to an older request than the current interface state. |
| Implementation | Delay choice A and let B respond first in the test environment. Verify that late A does not replace B. Repeat after a timeout, abandoned navigation and another attempt. |
| Verification | Only the current choice can update the view, and a timeout offers a meaningful next step. |
Fix the cause and repeat the test
Check request identity before updating and use cancellation where supported. A client stopping its wait does not mean a server-side operation was undone.
Repeat the same test after the change and add a nearby case that already worked. One successful case establishes that task in those conditions; it does not certify the whole website.
What the test establishes
Only the current choice can update the view, and a timeout offers a meaningful next step.