How to test a contact form properly

1. Define the expected end-to-end result

• Which fields are required?
• Where should the message or lead arrive?
• Should an autoresponse be sent?
• What should the user see after a successful submission?

2. Test validation deliberately

• Submit the empty form.
• Use an invalid email address.
• Test unusually long but reasonable input.
• Check whether validation is attached to the correct field and understandable without relying only on color.

3. Submit valid data and verify the real destination

Use a uniquely identifiable test message. After the interface reports success, verify the inbox, CRM, webhook destination, or other system that should receive it. If you cannot verify the destination, record that limitation rather than claiming full success.

4. Test failure behavior

• What happens if the server rejects the request?
• Does the form preserve user input when it fails?
• Is the error visible and actionable?
• Does the UI ever claim success when the underlying request failed?

5. Check duplicate submission and mobile use

• Double-click Submit and watch for duplicate requests/leads.
• Confirm the submit button is disabled or otherwise protected while sending where appropriate.
• Test the keyboard, field types, validation messages, and success/error states on mobile.
• Make sure cookie banners or sticky widgets do not cover the form controls.

6. Record evidence that another person can reproduce

A useful finding names the page, input conditions, steps, observed result, expected result, and evidence. “Form broken” is not enough for a developer to diagnose quickly.