Gravity Forms Testing

CheckView officially supports automated testing of Gravity Forms. Gravity 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 Gravity Forms block and forms embedded with the [gravityform] shortcode both work, including forms placed inside a reusable block (synced pattern).

Requirements

The CheckView helper plugin, installed and kept up to date. See Installing and Updating the CheckView Helper Plugin.
CheckView helper plugin 2.1.0 or newer if your site uses Gravity Forms Background Notifications. Older versions cannot redirect a notification that Gravity Forms sends in the background, so it would go to your real recipients.
CheckView helper plugin 2.3.3 or newer if your site uses Gravity Forms Zero Spam.
The form set to Active. Inactive forms and forms in the trash do not appear when you create a test flow.

What CheckView does on a Gravity Forms test

Automatic test generation. CheckView detects your active Gravity Forms 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. If Background Notifications is turned on, CheckView sends the test’s notifications during the submission itself so they are redirected like any other. Your real visitors’ notifications still go out in the background as normal.
Anti-spam and CAPTCHA handling. The Gravity Forms CAPTCHA field is removed for CheckView test sessions only, as are hCaptcha, Turnstile and honeypot fields. The Gravity Forms reCAPTCHA Add-On and Cloudflare Turnstile Add-On are switched off for the test session. CheckView also bypasses Akismet, CleanTalk, Gravity Forms Zero Spam, hCaptcha for WordPress and Simple Cloudflare Turnstile, and a test entry is never marked as spam. The Gravity Forms honeypot cannot quietly discard a test entry either. WP Armour is not switched off but simply satisfied: its hidden field is left empty, which is what a real visitor’s browser does, so tests pass with it fully active. See Automatic Disabling of Anti-Spam and CAPTCHA Plugins.
Honest validation. CheckView clears only anti-spam and CAPTCHA validation errors. Any other validation error, such as a new required field the test flow does not fill in, still fails the test, so a new required field shows up as a failed test rather than a quiet pass.
Integration suppression. When Disable Form Integrations During Tests is on, CheckView removes every add-on feed from the test submission, so Mailchimp, HubSpot, Zapier, Webhooks and the other feed-based add-ons do not run for it. See Disable Form Integrations During Tests.
Gravity PDF. PDFs are never generated for test notifications, whatever the integrations setting.
Feeds that run in the background. When integrations are allowed to run, CheckView keeps the test entry in Gravity Forms for about 15 minutes before removing it, so feeds that Gravity Forms processes in a background request can still load the entry and deliver it.
Database submission validation. The submission is copied into the CheckView tables and verified against the values the bot entered, then removed from Gravity Forms’ own entries. Gravity Forms stores each part of a Name or Address field separately, so each part is checked on its own. Date values are matched whatever display format the form uses.
Field coverage. Single Line Text, Paragraph Text, Drop Down including the enhanced (Chosen) multi-select, Checkboxes, Radio Buttons, Number, Name, Email, Phone including the international format with a country selector, Address, Website, Date, Time, List and Consent. See Form Field Support for the full list.
File uploads. Gravity Forms does not tell the browser which file types a field accepts, so CheckView reads the field’s “Accepted file types” note and uploads a matching sample. For multi-file upload fields CheckView waits for the upload to finish before it submits, rather than assuming it did.
Date fields. The calendar picker, the plain date field and the dropdown style are all supported, including date restrictions such as future dates only, no weekends and specific dates. Both the older calendar and the newer Gravity Forms date picker are handled. See Date Pickers.
Multi-page forms. CheckView navigates Gravity Forms’ page breaks automatically, waiting for each page to change before it continues. Forms using Gravity Perks Page Transitions are supported too.
Conditional logic. Fields hidden by conditional logic are skipped, including nested conditions, so the test fills in the form the way a visitor would see it.

Creating a Gravity Forms test flow

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

If your form is placed on the page by a page builder module rather than the Gravity Forms block or shortcode, its page may not be listed. Choose Add Custom URL and enter the page path.

Things to know

Which integrations are suppressed

Integration suppression covers add-ons that run as Gravity Forms feeds, which is how Gravity Forms’ official add-ons such as Mailchimp, HubSpot, Zapier and Webhooks connect. Custom code or a plugin that hooks directly into form submission, rather than registering a feed, still runs during a test. If you need to be certain a sensitive integration never fires, test against a staging environment.

Test entries stay for about 15 minutes

Every Gravity Forms test entry stays in your Entries list for about 15 minutes before CheckView deletes it. The deletion runs through WP-Cron, so on a low-traffic site, or a site with WP-Cron turned off and no server cron in its place, it can take longer. If an entry export or report runs in that window, it can include the test entry.

Testing your feeds end to end

To confirm a feed actually delivers, turn Disable Form Integrations During Tests off for that test flow. The test entry then reaches your connected tools with CheckView’s test data, including a CheckView email address, so plan for a test contact in your CRM or mailing list, or use the add-on’s conditional logic to skip entries whose email address ends in checkview.io.

List fields

CheckView fills the rows a List field shows when the page loads. It does not add or remove rows during a test.

Save and Continue

CheckView submits the form. It does not use the Save and Continue link, so saving a draft and resuming it later is not tested.

Multi-file uploads with restricted file types

For single file upload fields CheckView matches the accepted file types. For multi-file upload fields it does not read the accepted types and uploads a JPG sample, so a multi-file field that does not accept images may reject it.

Payment add-ons

CheckView does not switch Gravity Forms payment add-ons such as Stripe or PayPal into test mode. Test a form that takes a payment on a staging site where the payment add-on is in test mode.

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