A launch test should verify the complete handling chain
Test the complete path from submission to the receiving view before sending campaign traffic. A working front-end confirmation does not prove the record reached the intended destination.
Before sending campaign traffic, test accepted submission, stored record, notification, routing and duplicate behavior. A successful visual form preview does not verify delivery. Include failure cases that can occur on actual devices.
A worked example
A hypothetical form passes a desktop submission test but loses an attached file on mobile. Another sends two notifications on retry and creates duplicate rows. Both need repair before their counts can be trusted.
How to apply it
- Use fictional clearly labeled details and approved test recipients.
- Test required-field errors, success, retries and the relevant mobile path.
- Inspect the final record and responsible recipient, not only the confirmation message.
What the result can establish
Keep a short test record with expected and observed results. Avoid sending unapproved messages or using real client data as fixtures. Retest affected paths after a repair rather than repeating an entire unrelated checklist.
Reference: W3C WAI: validating forms.
Supporting documentation
W3C WAI: validating formsGoogle Analytics: recommended eventsGoogle Analytics: measurement documentation