🎉 Celebrate with 10% OFF on All Products! Use Code: GFEX10 Or Buy Any 2+ Items for 30% OFF with Code: GFEX30!
Guides & Tutorials October 30, 2026

How to Test Gravity Forms on a Live Site Without Side Effects

GravityExtra
How to Test Gravity Forms on a Live Site Without Side Effects

You changed a Gravity Form. Maybe you added a field, renamed a choice, connected a CRM or moved the thank-you page. Now you need to know that it works, and the only honest test is to submit the real form on the real site. The trouble is that a real submission does real things: the sales team gets a fake lead, a customer receipt goes to whatever address you typed, your CRM and mailing list get a new contact, a row lands in the spreadsheet, and the entries list collects another “test test” that nobody deletes. The Gravity Forms Test Mode add-on lets you test any form on your live site without those side effects.

This guide explains why testing live forms is risky, what a safe test should and should not do, and how to test Gravity Forms from the admin bar or with a private link for a client, then find and clean up the test entries afterwards.

Why testing a live form is risky

A Gravity Form is the front of a small machine. Behind the fields sit notifications to your team, to the person who filled in the form and to addresses chosen by routing rules. There are confirmations, conditional logic, calculations, and feeds that pass every entry on to other systems: a CRM, an email marketing list, a help desk, a spreadsheet or a webhook. When you submit the form to test it, every part of that machine runs exactly as it would for a customer.

That leads to familiar problems. Colleagues learn to ignore new-lead emails because half of them are tests. A test contact in the CRM triggers a welcome sequence or a sales task. A test address lands on a mailing list and is counted in your reports. Entry counts, conversion numbers and exports include submissions that were never real. And because each test causes noise, people test less often, so the next broken form reaches real visitors first.

Some teams work around this with a copy of the form, a staging site or a temporary change to the notification addresses. Each workaround has a cost. A copied form drifts away from the real one. A staging site often has different plugins, different email settings and different feeds. Changing notification addresses by hand is easy to forget to undo, which is how real leads end up in a developer’s inbox for a week.

What a safe test should do

A good test runs the real form, on the real page, with the real fields, conditional logic, calculations and confirmations. What should change is only what happens after the submission:

  • The entry should be saved, so you can check the values, but it should be clearly marked as a test.
  • Notifications should be sent, so you can check subjects, layout and merge tags, but only to the person who tested.
  • Add-on feeds should not push test data into your CRM, mailing list, spreadsheet or other connected services.
  • The tester should see, before they press the button, exactly what will happen.
  • Test entries should be easy to find, keep out of your unread count, and be removed in one step.

That is what Gravity Forms Test Mode does.

Testing from the admin bar

After you install the add-on and activate your licence in Forms → Settings → Test Mode, administrators see a new item in the admin bar: Form test mode: Off. Click it and it turns orange with the time left, for example Form test mode: On (2 h left). Test mode switches itself off after the time you choose in the settings, from 30 minutes to 8 hours, so it is never left on by accident. You can let other roles test too, for example editors who maintain the forms.

Now open any page with a form. Above the form a ribbon explains what will happen: the submission is saved as a test entry, notifications go only to your address, and add-on feeds are skipped. If the form takes payments, the ribbon adds a reminder that payments are real unless your payment provider is in its own test mode.

https://gravityextra.com/wp-content/uploads/2026/10/gfxtm-ribbon.png

Fill in the form and submit it. The confirmation appears as usual, with a short note on top: the number of the test entry and what was done with its notifications and feeds. In your inbox you find every notification of the form, each with [TEST] at the start of the subject, all sent to you. The Send To address, routing rules, CC and BCC of each notification are replaced for the test, so nobody else receives a copy. The Reply To is kept, so you can still check that a reply would reach the address typed into the form.

Testing with a private link

Often the person who should test a form has no account on your site: a client approving a new enquiry form, a colleague in another team or an agency partner. For them, create a test link. In Forms → Test Mode choose the form, give the link a name such as Client review, enter the address that should receive the test notifications, and choose how long the link works: one day, seven days or thirty days. The add-on finds the page that shows the form for you.

Send the link. Whoever opens it sees the same ribbon and submits the form as a test until the link expires or you revoke it. The secret part of the link disappears from the address bar as soon as it is opened and is kept in a cookie for the life of the link. The link only covers its own form, so other forms on the site stay real for that visitor. If someone changes the link, or opens it after it expired or was revoked, nothing is tested and the page says the link is no longer valid, so nobody believes they are testing when they are not. You can revoke one link, or every link at once.

Notifications, feeds and payments

You decide what a test submission does, once for the whole site and, where needed, differently for a single form:

  • Notifications only to the tester is the default. Every notification is sent to the tester with [TEST] in the subject, which is ideal for checking wording and merge tags.
  • Do not send any notification suits forms where emails do not matter for the test, such as a quick check of an event sign-up.
  • Send them as usual with [TEST] is useful when the team should see the real email but know that it is a test.

For feeds, the default is to skip add-on feeds for test entries, and each skipped feed is noted on the entry, for example Test entry: CRM feed “Leads” skipped. If you want to test a feed itself, choose Run add-on feeds as usual for that form. Payments are never faked: payment add-ons always run, because a test that pretends to charge a card would prove nothing. Use your payment provider’s test mode for paid forms.

The rules are stored on the entry itself. That matters more than it sounds. If your site sends notifications in the background after the page has loaded, or if you resend a notification from the entry screen a week later, the notifications of a test entry still go only to the tester.

Finding and cleaning up test entries

Every test submission is a normal Gravity Forms entry with a Test entry mark and a note that says who tested and how. Test entries are marked as read, so they do not add to the unread count. On the entries list a Test filter link shows only test entries with their number, and Test entry can be shown as a column. On the entry screen, a Test entry box says who tested it, whether it came from the admin bar or a test link, and where its notifications go.

https://gravityextra.com/wp-content/uploads/2026/10/gfxtm-entry.png

Entries that were sent as tests before you installed the add-on can be marked with the bulk action Mark as test entry, and a real entry marked by mistake can be fixed with Not a test entry. When you are done, click Move test entries to the Trash on the Test Mode page or in a form’s Test Mode tab. Only test entries are moved, and Gravity Forms keeps them in the Trash until you empty it. If you prefer, switch on automatic clean-up: test entries older than one hour, one day, three days, seven days or thirty days are moved to the Trash or deleted every hour. Clean-up is off until you choose it.

The test log

The Forms → Test Mode page brings everything together: your own switch, the test links with their recipients and end dates, the number of test entries per form, and the test log. The log lists the latest test runs with the form, the entry, who tested and what happened to each notification and feed: sent only to the tester, not sent, or sent as usual with [TEST], and which feeds were skipped. When a client says they tested the form yesterday, you can see exactly what they submitted and where the emails went. The log never stores what was typed into the form.

https://gravityextra.com/wp-content/uploads/2026/10/gfxtm-page.png

A testing routine that works

With safe tests, testing becomes a habit instead of a risk. A simple routine for every form change looks like this:

  1. Make the change in the form editor and save the form.
  2. Switch test mode on from the admin bar and open the page with the form.
  3. Submit the form once for each important path: each choice that changes conditional logic, each routing rule, each calculation you care about.
  4. Check your inbox: subjects, merge tags and layout of every notification.
  5. Check the entries and the test log, then move the test entries to the Trash.
  6. If a client or colleague needs to approve the form, send them a test link that expires in a day or a week.

Agencies can use test links as part of sign-off: the client tests the real form on the real site, the notifications reach the agency’s address, and nothing reaches the client’s CRM until the form is approved. Site owners can let editors test the forms they maintain without giving them access to notification settings.

Frequently asked questions

Does test mode change the form for visitors? No. Only people with a tester role who switched test mode on, and people who opened a valid test link, submit tests. Every other visitor submits the form as usual.

Can a test link be shared further? Anyone who has the link can test that one form until the link expires. Test notifications still go only to the address you chose for the link, and you can revoke it at any time.

Does it work with page caching? Logged-in testers are never served cached pages. For test links the submission is always a test; on a page served from a cache, the ribbon may only appear after the page is loaded fresh.

Can I keep one form always real? Yes. In the form’s Test Mode tab, switch off Allow test submissions on this form.

Is there a command line tool? Yes. With WP-CLI, wp gf-test list counts test entries, wp gf-test purge moves them to the Trash or deletes them, wp gf-test links lists live test links and wp gf-test log shows the latest runs.

Getting started

Install and activate the add-on, activate your licence key under Forms → Settings → Test Mode, choose who can test, and click Form test mode in the admin bar. Your next form change can be tested on the live site in a minute, with nothing reaching your team, your customers or your CRM. The add-on works with Gravity Forms 2.9 and newer. Read the full set-up guide on the Gravity Forms Test Mode documentation page, or see pricing and features on the Gravity Forms Test Mode add-on page.

0
0
Your Cart
Your cart is emptyReturn to Shop
🔥 FREQUENTLY BOUGHT TOGETHER
Complete Combo & Save 40%!
ITEM IN YOUR CART
Gravity Forms Klaviyo Add-on
$39.00/yr
+
🎁 RECOMMENDED ADD-ON SAVE 40% OFF
Original Price: $39.00/yr
Bundle Special Price: $23.40/yr