Forminator Forms Testing

CheckView officially supports automated testing of Forminator forms. Forminator appears as a form plugin when you create a test flow, and CheckView builds the test steps for you, no manual step configuration required. Forms embedded with the shortcode and forms embedded with the block editor both work.

Requirements

CheckView helper plugin 2.4.0 or newer. Forminator support was added in 2.4.0. On older versions your Forminator forms will not appear when you create a test flow. See Installing and Updating the CheckView Helper Plugin.
CheckView helper plugin 2.4.2 or newer for two additions: integration suppression, and validating each part of a multi-part field separately.
The form’s Store Submissions setting left on. With it off, Forminator keeps no entry, so the test still runs but there is nothing to validate the submitted values against.

What CheckView does on a Forminator test

Automatic test generation. CheckView detects your Forminator forms, finds the pages they appear on, and generates the test steps automatically.
Email suppression. Form notification emails are redirected to the CheckView test inbox during a test run, so your real recipients never receive test submissions. CC and BCC recipients are stripped.
Anti-spam and CAPTCHA handling. Forminator’s own CAPTCHA field is removed for CheckView test sessions only, which covers reCAPTCHA v2, reCAPTCHA v3, hCaptcha and Cloudflare Turnstile. Forminator’s built-in Akismet and spam protection are bypassed for test sessions, and CheckView also switches off separate anti-spam plugins: CleanTalk, hCaptcha for WordPress and Simple Cloudflare Turnstile. Two more are not switched off but are simply satisfied, so tests pass with them fully active: a honeypot field is left empty, which is what a real visitor’s browser does, and WP Armour’s check is met by the same browser automation. See Automatic Disabling of Anti-Spam and CAPTCHA Plugins.
Integration suppression. When Disable Form Integrations During Tests is on, CheckView hides the form’s add-on feeds from the submit path, so Mailchimp, webhooks and the other connected add-ons do not fire for test submissions. The entry is still saved so submission validation can run. See Disable Form Integrations During Tests.
Database submission validation. The submission is copied into the CheckView tables and verified against the values the bot entered, then removed from Forminator’s own entries so your submissions stay clean. Multi-part fields (name, address, date and time) are validated part by part.
Field coverage. Name, email including confirm-email, all three phone formats, address, website, text, textarea including the rich text editor, number, currency, radio, checkbox, every select variant including the searchable one and the custom “Other” option, password and consent. See Form Field Support for the full list.
Number and currency limits. CheckView reads the minimum and maximum your form actually enforces, not just the field’s HTML, so a currency field with a minimum above zero is filled with a value the form accepts.
File uploads. Single and multi-file upload fields are both supported. For multi-file fields CheckView confirms the file really finished uploading before it submits, rather than assuming it did.
Date and time fields. The calendar picker, the dropdown style and the text-input style are all supported, including date restrictions such as future or past only, weekdays, disabled dates, ranges and offsets. Time fields are supported in both the dropdown and number-input styles, in 12 and 24 hour formats, and CheckView respects a configured time limit.
Multi-step forms. CheckView navigates Forminator’s pagination automatically, including conditional steps.
Both submit modes. Forms using AJAX submission and forms submitting as an ordinary POST are both covered, as are forms that redirect after submitting.

Creating a Forminator test flow

Forminator works the same as any other supported form plugin. From your website dashboard, click Add Test Flow, choose Forminator, select your form and URL, set a schedule, and CheckView builds the steps. Full walkthrough: Creating a Form Test Flow.

Things to know

Field Group repeaters

CheckView fills the fields inside a Field Group and validates them. It does not add extra repeater rows during a test: Forminator gives each row you add a new random identifier, so there is no reliable way to target the added row or match its values afterwards.

Payment fields

The Stripe and PayPal fields are not supported. A form that requires one cannot be completed by a test.

Quizzes and polls

CheckView tests Forminator’s forms. Quizzes and polls are separate Forminator modules and are not tested.

Add-ons from other plugins

Integration suppression covers the add-ons Forminator itself registers. An add-on introduced by a separate plugin very late in the WordPress load may still run during a test. If you need to be certain a sensitive integration never fires, test against a staging environment.

Forminator is one of the form plugins covered by automated WordPress form testing.