Skip to content
CheckView
Get Started

Fluent Forms Testing

CheckView officially supports automated testing of Fluent Forms. Fluent Forms 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

What CheckView does on a Fluent Forms test

  • Automatic test generation. CheckView detects your published Fluent Forms, finds the pages they appear on (including pages that use a synced pattern containing the form), and generates the test steps automatically.
  • Email suppression. Every Fluent Forms email notification on the form is 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. Fluent Forms’ built-in reCAPTCHA (v2 and v3), hCaptcha and Cloudflare Turnstile are switched off for CheckView test sessions only, as are its honeypot, its token-based spam protection and its Akismet check. CheckView also handles CleanTalk, 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 keeps Fluent Forms’ email notifications and removes every other integration feed from the test submission, so Mailchimp, webhooks, Slack, Zapier, CRM feeds and the rest do not fire. 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. The copy is taken at a point in Fluent Forms’ submit process that an error in another plugin cannot interrupt, so a misbehaving add-on does not cause a false failure. The entry is then removed from Fluent Forms’ own entries (see Test entries are removed after a short delay).
  • Field coverage. Name, email, text, mask input, textarea including rich text, address, country, number, phone including the country picker, website, password, radio, checkbox, the searchable and multi-select dropdowns, Terms and Conditions and GDPR Agreement. See Form Field Support for the full list.
  • Payment items. Amount choices, subscription options and payment method selectors are targeted by their field name rather than the ID Fluent Forms regenerates on every page load, so the steps keep working from one run to the next.
  • File uploads. CheckView uploads a sample file and waits for Fluent Forms to confirm the upload has finished before it submits, rather than assuming it did. See Testing Forms with File Uploads.
  • Date and time fields. Filled with the Assign Date step, including restrictions such as future only, past only, a set range, a custom date format, 24 hour time and a limited time window. See Date Pickers.
  • Multi-step forms. CheckView navigates Fluent Forms’ Next buttons automatically.

Creating a Fluent Forms test flow

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

Things to know

Test entries are removed after a short delay

Fluent Forms Pro can run integrations as queued background jobs that load the entry a little after it is submitted. So that those jobs still find the entry when integrations are allowed to run, CheckView removes the test entry from Fluent Forms about 15 minutes after the test rather than immediately. You may briefly see a test entry in your Fluent Forms entries list. The removal is scheduled through WP-Cron, so if WP-Cron is disabled on your site and no server cron replaces it, test entries remain until cron next runs.

What integration suppression covers

Suppression works on Fluent Forms’ own list of integration feeds: email notifications are kept and every other feed type is dropped for the test submission. Code that a separate plugin attaches directly to a Fluent Forms submission, outside that feed list, is not affected and may still run. If you need to be certain a sensitive integration never fires, test against a staging environment.

Forms CheckView cannot find on a page

CheckView finds a form’s pages by looking for the Fluent Forms shortcode or block in your content. A form placed through a page builder widget, a theme template or a popup may not be listed against its page. In that case, choose Add custom URL in the URL picker when you create the test flow and enter the page’s path.

Card payments

CheckView does not complete card payments through Fluent Forms’ payment gateways. A form that requires a card payment before it will submit cannot be completed by a test.

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