How do I test forms?

What to actually check

A form "working" visually isn't the same as working correctly. For every form on the site:

1. Submit with valid data — confirm a success message and that the data arrives where expected (a database table, an email via Resend, a Stripe checkout, etc.).
2. Submit with missing required fields — confirm validation blocks it with a clear message, not a silent failure.
3. Submit invalid formats — a malformed email, letters in a phone field, an absurdly long string — and confirm the form rejects or handles it gracefully.
4. Double-submit — click submit twice quickly and check you don't get duplicate database rows or duplicate emails.
5. Refresh mid-fill — check whether losing unsaved input is acceptable for that form, or whether it needs a warning.

Checking where the data actually goes

If the form writes to your database, ask Lovable to confirm:

Show me where submissions from the [contact/signup] form are stored, and confirm the table has RLS so only I can read submitted entries.

If it sends an email, send a real test submission and check the inbox (including spam) rather than trusting a "sent" message alone.

A prompt for validation

Add proper validation to the [form name] form: required fields, email format checking, and a clear inline error message per field.

What usually goes wrong

• No server-side validation — client-side checks can be bypassed, so malicious or malformed data still reaches your database unless rules exist there too (RLS/constraints).
• Contact forms with no rate limiting, letting spam bots flood submissions.
• Success message shown even when the underlying save/send actually failed.
• Forms that don't work with a password manager or autofill, frustrating real users.

See also /questions/how-do-i-test-user-registration for sign-up forms specifically.