What a successful check tells you.
A live test enters synthetic details, submits a compatible form and checks its configured success state. It can reveal a missing field, a form that no longer loads or a confirmation that fails to appear.
A green result proves that specific assertion passed. It does not confirm that an email reached an inbox, that a CRM saved the enquiry or that a person replied. Check those downstream steps separately.
Set it up deliberately, then let it repeat.
- Verify the hostname. Add a DNS record or the supplied verification file.
- Map the form. Use clearly synthetic values and a stable target.
- Run a dry test. Confirm that the intended form and fields are found without submitting.
- Approve live testing. An owner or admin unlocks live submission after reviewing the dry result.
- Review the confirmation. Use a success message that appears only after the submission completes.
Live submission is limited to once every 24 hours per form monitor. Plan intervals apply to availability and content checks; they do not turn form submissions into five-minute tests.
Check the fit before creating an account.
Public, single-step native contact and quote forms with predictable fields are suitable candidates. CAPTCHA, login gates, payments, file-heavy workflows and complex multi-step applications are not a suitable starting point.
WordPress compatibility depends on the rendered form, not simply the plugin name. Use the free form compatibility checklist to identify the questions to answer first.