Recovery tests must respect intentional retry cooldowns

When fault-injection tests retry a form after a dropped request or lost response, distinguish an intentional cooldown from broken recovery. Observe and dismiss the error dialog, verify immediate retry is throttled when policy requires it, then retry after the configured interval and check persisted state. An enabled button alone does not prove the next attempt may reach the server. Otherwise the test can report a missing second request even though the protective behavior is correct. This method validates recovery timing; it does not prove exactly-once persistence or downstream effects, which need separate record checks.

Applies when: Browser tests inject transport failures into forms with retry throttling. Keywords: fault injection retry cooldown recovery modal network persistence