Catching Broken Forms Before the Client Does

The Challenge

This agency maintains more than 50 WordPress sites for Swiss small and mid-sized businesses. On most of them the contact form and the WooCommerce checkout are the only things on the site that actually bring in money, which makes them the last things anyone wants failing unnoticed.

Unnoticed is exactly how they fail. A plugin gets updated, or a spam-protection rule changes, and the form still looks completely fine when you submit it. No lead ever arrives. The agency would find out weeks later, when the client asked why things had gone so quiet.

The alternative was testing every form and every checkout by hand after every update. At that number of sites it does not get done properly, it gets skipped. And when something was broken there was no way to tell when it started or which change caused it.

The Solution

The agency now keeps between 50 and 100 forms and checkouts on automated CheckView tests. Each one submits a real entry on its own schedule, so a form that has quietly stopped delivering is caught the same day instead of weeks later. The test history then shows when it stopped working.

What the team values most is what arrives with a failure. Every test run keeps screenshots, a video recording and the browser console log, so the failing step is visible without anyone reproducing the problem first. At this number of sites, that saves a lot of time.