Check forms and checkout after every WordPress plugin update
Plugin, theme and core updates break forms and checkout while the site stays up. A scheduled plain-language test catches it the morning after, not weeks later.

Updates are the risk you cannot skip#
WordPress sites have to be updated: core, theme and plugins, for security. Every update can change something else. The support forums are a long record of it: a contact form that stopped working after a WordPress update; a Gravity Forms release that broke notifications when several addresses were notified; a Contact Form 7 update that stopped sending until the previous version was restored.
A guide on broken WordPress forms sums up the timing problem: the culprit in one case was a routine security plugin update that changed how forms were validated, and the client would never have known until someone complained.
Uptime monitoring does not see any of this. The site is up. The form is broken.
A functional check after each update#
The answer is a test of what the update could break, run after the update, every time:
Open https://client.example/contact.
Submit the form empty and check the error names the missing fields.
Fill in "QA Test", this run's email address and "Update check, please
ignore", and send.
Check the page says the message was sent and the confirmation email
arrives.For a WooCommerce shop, add the money path in test mode:
Add "Sample product" to the cart, open the cart and go to checkout.
Check the checkout page shows the product, the total and the payment
options, without an error notice.When to run it#
- On a schedule. If updates run automatically, put the tests on a nightly schedule after the update window. A failed run emails you with what was seen and a replay.
- After a manual update. Press Run all on the client's project once you have updated.
- From your deploy tool. If updates go through a pipeline, the command-line tool runs the project's tests and exits non-zero on a failure.

What it costs#
Each run counts toward your plan. Two tests per client site, nightly, is about 60 runs a month per site. Agencies with many sites usually run nightly checks on the sites with forms or checkout that earn money, and weekly on the rest.
This post is part of Find the bug before your client does.
Filed underWebReleases and regressionsClient sites