Formidable Forms Testing

CheckView officially supports automated testing of Formidable Forms. Formidable 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 Formidable shortcode are detected automatically, including shortcodes placed inside a reusable block.

Requirements

The CheckView helper plugin, kept up to date. Formidable handling lives in the helper, and fixes to it ship with helper updates. See Installing and Updating the CheckView Helper Plugin.
Formidable Forms active on the site. Formidable Forms Pro runs on top of the core plugin, so Pro sites are covered too.
A published form. Draft forms are not listed when you create a test flow.

What CheckView does on a Formidable test

Automatic test generation. CheckView detects your published Formidable forms, finds the pages whose content contains the form’s shortcode, and generates the test steps automatically.
Email suppression. The recipient of the form’s Send Email actions is replaced with the CheckView test inbox during a test run, so your real recipients never receive test submissions. CC and BCC recipients are stripped. CheckView then confirms the notification actually arrived.
Anti-spam and CAPTCHA handling. Formidable’s CAPTCHA field is removed from the form and from validation for CheckView test sessions only, whichever provider it is set to (reCAPTCHA, hCaptcha or Cloudflare Turnstile). Formidable’s honeypot check is switched off for the test, and the honeypot field is never filled. Akismet is bypassed for the test session, and CheckView also handles hCaptcha for WordPress, Simple Cloudflare Turnstile and WP Armour. See Automatic Disabling of Anti-Spam and CAPTCHA Plugins.
Integration suppression. When Disable Form Integrations During Tests is on, CheckView skips the form’s actions for the test submission, except Send Email, Register User and the confirmation action. Webhooks (the API action), marketing and CRM actions and the rest do not fire. See Disable Form Integrations During Tests.
Database submission validation. The entry is copied into the CheckView tables and verified against the values the bot entered, then removed from Formidable’s own entries in the same request that created it, so test entries never build up in your entry list or anything that reads from it. Name fields are validated part by part in all three layouts (first and last, last and first, and first, middle and last).
Date and time fields. Date fields are filled through Formidable’s calendar picker, including the inline calendar, and CheckView picks an available date on every run so the step does not go stale as time passes. Time fields are supported as dropdowns, in 12 and 24 hour formats and as a single time dropdown. Formidable stores times in 24 hour form, and CheckView matches a 12 hour value against it correctly.
Dropdowns. Standard dropdowns and Formidable’s autocomplete dropdowns are both filled.
File uploads. Formidable’s drag-and-drop upload field is supported. CheckView uploads a sample file through the field’s own file input without opening a file dialog, and confirms the stored entry contains the upload.
Multi-page forms. CheckView detects Formidable’s page breaks and moves through each page with the form’s Next button, waiting for each new page to load, before pressing the final submit button. Previous buttons are ignored. If a visitor saves a draft partway through, that draft does not end the test; only the final submission does.

Creating a Formidable test flow

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

Things to know

Forms added with the block editor or a page builder

CheckView finds the pages a Formidable form appears on by looking for the Formidable shortcode in the page content. A form placed with Formidable’s block or with a page builder’s form widget is not listed against its page automatically. The form itself is still listed, so choose it, then use Add Custom URL and enter the page path. The test runs normally from there.

Send Email, Register User and the confirmation action are kept even when integrations are disabled. On a registration form, every test run registers a new WordPress user, and CheckView does not remove those accounts. For registration forms, test against a staging site or plan to clear the test accounts periodically.

Repeaters and embedded forms

Formidable saves the rows of a Repeater section, and the fields of an Embed Form field, as separate child entries. CheckView does not compare the values in those child entries with what was entered, and it does not add extra repeater rows during a test. The child entries are removed along with the main test entry, so nothing is left behind.

Confirmation redirects

The confirmation action is not suppressed, so a form set to redirect after submission still redirects during a test. That is expected and does not affect the result.

Add-ons from other plugins

Integration suppression covers integrations that run as Formidable form actions. An integration that hooks into the submission some other way may still run during a test. If you need to be certain a sensitive integration never fires, test against a staging environment.

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