A WordPress form testing checklist should follow an enquiry from the public page to the team that handles it. A loaded page or a success banner is useful evidence, but neither closes the whole loop. Use this checklist when onboarding a maintenance client and after changes to forms, themes, plugins, hosting or mail configuration.
Before you submit: agree on the test
- Confirm you own the website or have explicit permission to test it.
- List each important form, its public URL, normal recipient and business owner.
- Use a clear synthetic name and a message such as “Agency monitoring test — no reply required.” Do not use real customer enquiries or somebody else’s contact details.
- Check whether the form triggers CRM entries, autoresponders, notifications, bookings or other actions. Decide how labelled tests will be handled.
- Keep payment, file-upload, sensitive-data and complex conditional journeys in a separately reviewed test plan.
Browser checks: test the published experience
- Open the public page. Start signed out of WordPress so an administrator-only behavior does not conceal a visitor problem.
- Review labels and controls. Ensure required fields, options and validation messages make sense. Use valid synthetic values for the happy path.
- Check a narrow screen. Confirm fields and the submit button are usable without horizontal scrolling, clipped labels or a hidden response.
- Submit once and record the result. Note the test time, the exact response and the form/page involved. Check that a recent field rename did not break the expected behavior.
- Review failure paths manually. On a controlled test, check that invalid required input produces useful validation rather than appearing to submit successfully. Keep visitor-facing anti-abuse protection enabled.
Email checks: confirm the destination separately
Ask the normal recipient to verify that the expected notification actually arrived. Check the destination and sender settings for the exact form, then review transport logs and mailbox filtering if it did not. Preserve a test reference so the browser event and message can be matched without copying customer information.
WPForms notification settings live under Settings → Notifications in its builder. Contact Form 7 exposes its notification configuration in the Mail tab. Follow the relevant plugin’s documentation rather than assuming every form uses one global destination.
Operational checks: make the next investigation easier
- Write down who receives a failure alert and who owns the fix.
- Record a last-known-good manual result after a relevant update.
- Recheck important forms after changing mail credentials, sender domains or notification destinations.
- Distinguish a browser failure, missing monitoring receipt and an inconclusive test in the incident record.
- Decide how often a synthetic check is useful without generating an unnecessary volume of client notifications.
Turn the checklist into a monitoring routine
LensShift can repeat configured browser submissions and verify a uniquely matched monitoring email for compatible forms. Start with a manual baseline, connect the companion plugin, and run an on-demand check before scheduling. Set up a separate monitor for each selected form/page; do not assume one contact form covers every enquiry journey on a website.
A scheduled check runs at intervals. It does not exercise all field combinations, every browser or every moment between checks. Keep manual testing for accessibility, complex interactions and business outcomes that fall outside the monitor’s configured path.
What a pass means: the configured browser submission succeeded and a matching email reached LensShift’s monitoring mailbox. It does not prove delivery to your client’s normal inbox, cover every visitor journey, or guarantee continuous uptime.
A compact handover record
For each form, keep: page URL; selected form; test date/time; synthetic-data convention; browser outcome; normal-recipient confirmation; monitoring outcome; owner; and next action. This makes a care-plan handover useful without inventing a guaranteed uptime percentage.