Test your form before publishing

1. Start with a test endpoint

This guide covers the safe default workflow and the checks that matter before production. Create a clearly named test form and allow your development or staging origin. Use non-sensitive sample values and a verified mailbox you control. Test forms share the owner’s monthly allowance; accepted non-spam tests count too. For webhooks, use a test destination that will not trigger real orders or other production actions.

2. Verify one complete submission

Open the page from its actual HTTP or HTTPS origin, fill every field, and submit once. Inspect the POST response, then find the record in Submissions. Compare names and values, including checkbox arrays, empty selections, and any uploaded files. For a native form, check the thank-you destination; for AJAX, check the inline response and field reset. Saved drafts are not final submissions and should not be treated as inbox receipt.

3. Verify delivery independently

Inspect the submission’s Delivery status, check the notification mailbox, and open a reply to confirm its recipient. Test an enabled autoresponder and webhook separately. For attachments, open the secure download link. If the record is in Spam, inspect its signals before changing protection. A successful POST does not prove mail delivery.

4. Exercise failure handling

On the test form, try an origin that is not allowed, a paused endpoint, invalid visible input, and an oversized file if uploads are enabled. Mock a 429, a server error, and an unreadable or interrupted response in your frontend test setup rather than flooding the live API. Confirm that values remain after errors, Retry-After is honored, and controls recover. Use the same idempotency key and payload when testing a retry of one final request.

5. Check accessibility and progressive behavior

Complete the form using a keyboard and test with a screen reader and increased zoom. Confirm labels, required-field messages, and response announcements are understandable. If you promise a no-JavaScript fallback, disable JavaScript and verify the native action and redirect. A CAPTCHA-dependent form may require JavaScript; make the requirement clear.

6. Verify the production endpoint

Before publishing, replace the test endpoint, review the production origin and redirect allowlists, and check recipients, Reply-To, CAPTCHA, and delivery destinations on the production form. These settings are not automatically copied from a test form. Send one final non-sensitive test from the deployed page. Preserve any needed records before archiving or deleting tests; deletion does not restore accepted-submission quota.

• Development and production forms
• Notification email is missing
• Idempotent submissions