qa-test-idempotency

Duplicate form submissions are prevented by verifying that the submit button disables or guards against immediate repeat clicks. This Skill probes for such protections by simulating rapid double-clicks and inspecting outcomes to catch missing submit-lock mechanisms.

Double-submit detection works by running an in-page asynchronous browser evaluation that autofills required fields and submits twice in quick succession. It inspects the submit-button state to verify duplicate records are not created during workflows.

The best way to test idempotency is using a single browser-side evaluation probe that fills required inputs, triggers duplicate submissions, and reports high-severity findings. This validates form safety without needing multi-step hand-driving.

Yes, duplicate record detection requires visible forms with required-input autofill. It applies the in-page asynchronous probe to inspect submit-button states and ensure duplicate orders, tickets, or accounts are not generated.

Rapid clicking on submit controls creates duplicate records when the form lacks submit-lock protections. The Skill catches this by inspecting whether the first submit disables the button to prevent immediate repeat clicks.

Yes, you can use browser automation to test form validation for duplicate submits. The Skill utilizes an in-page asynchronous browser evaluation probe to inspect submit-button states and verify protection against duplicate records.