Forms and checkout, tested on the test copy before every risky update

2 min readBy the Verploy team

A form or checkout test on the test copyBeforedoes theform work?Updateon thetest copyAfterfill in,send, checkShopadd to cart,open checkoutResultworks? live.broke? held backNothing is ever paid or ordered. The test copy sends no email.

A page can look perfect and still be broken. The contact form sends nothing, the quote form gives an error, the checkout does not open. For a client, that is worse than a layout glitch: it costs them leads and orders, often for days before anyone notices.

What Verploy tests

  • Forms from Contact Form 7, Gravity Forms and WPForms are really filled in and sent, and Verploy checks that the confirmation appears.
  • WooCommerce: a product goes into the cart and the checkout page must open.
  • This happens on the test copy, before the update and after it.

Safe by design

These tests never pay and never order. The test copy sends no email and blocks outgoing requests, so a test entry never reaches your CRM, a mailing tool or a payment provider. Forms with a captcha are skipped, because a captcha exists to stop exactly this kind of automated test.

A safe update that was held back on the test copy (example data)
When a test fails on the copy, the update is held back. (Example data.)

What happens when a test fails

If a form or the checkout worked before the update and no longer works after it, Verploy holds the update back. Your live site is not touched, and you get a plain explanation of what failed.

Want to see it on your own sites? Start free on up to 3 sites, no credit card.