BLOG
BlogTopic

Testing every release for regressions

Catching what a change broke elsewhere: a test per bug, a check after every deploy, and tests that survive a redesign.

GuidesWebRelease testing for product teams: a guideCheck every deploy like a customer would without a QA department: which journeys to test, where to run them, how to hear about failures and how to keep the suite alive.2 min read GuidesiPhone and iPadAndroidMobile release testing: a guide for app teamsFor iOS and Android teams: tests that survive a redesign, App Store review, builds for CI, an agent that tests its own build, and the states other tools miss.2 min read GuidesWebIt works in preview and breaks in production. Test the live addressAI app builders blur preview and production, so the version you clicked through is not the one users get. Test the deployed address after every deploy instead.2 min read GuidesWebFix one bug without breaking another: one bug, one testAI-built apps fall into a loop where each fix breaks something that worked. Keep a saved test for every bug you fix and run them all after each change.2 min read GuidesWebTen tests to run before you share your AI-built appA pre-launch checklist for apps built with Claude Code, Cursor, Lovable or Bolt, written as ten plain-language tests you can run on the live address today.2 min read GuidesWebTest every Vercel preview before you mergeRun your saved plain-language tests against each pull request's preview, including previews behind Vercel Deployment Protection, and fail on a regression.2 min read GuidesWebTest Stripe checkout and plan upgrades in test modeBilling bugs cost money twice. A plain-language test goes through Stripe Checkout in test mode, comes back and checks the plan changed, plus declines and 3D Secure.2 min read GuidesWebRun browser tests after every deploy with GitHub ActionsA small set of plain-language release checks that run on each deployment, fail the job on a broken journey, and keep the replay next to the commit that broke it.2 min read GuidesWebTests that survive a redesign: why selector tests breakTest maintenance is the cost that kills end-to-end suites. Why tests tied to selectors fail after UI changes when the app still works, and what to write instead.2 min read GuidesWebCheck AI-written code before your customers doTeams ship more code than anyone reviews line by line. Checking each deploy from the outside, as a customer would, catches what review and unit tests miss.2 min read GuidesWebRun your key journeys against production every nightDeploys are not the only thing that breaks an app. Email providers, payment settings and third-party scripts change too. A nightly schedule catches what no deploy caused.2 min read GuidesWebTest admin and member roles: what each person can see and doPermission bugs show a member a button they should not have, or hide one an admin needs. Test each role with its own stored account and check the screen for both.1 min read GuidesWebRelease checks for a startup with no QA teamNo QA engineer, two deploys a day, and a manual click-through that gets skipped. A minimal release check that a small team can keep: five tests, one gate, one channel.2 min read GuidesWebFlaky tests, and what a test verdict should be allowed to sayA test that passes and fails on the same code teaches people to ignore it. Why a verdict needs room to say blocked or inconclusive, and how to find flaky tests.2 min read GuidesWebTest search, filters and sorting without hard-coding the dataSearch boxes with suggestions, long lists, sorting and direct links are where list pages break. A plain-language test types, picks, scrolls, deletes and reads the result.1 min read GuidesWebTurn your release checklist into tests that run themselvesThe checklist in the wiki gets skipped on busy days. Move each line into a plain-language test, run them from CI or a coding agent, and keep the evidence per release.2 min read GuidesWebTest receipts, notifications and other emails your app sendsOrder receipts, mention alerts and weekly digests break without anyone noticing. A run with its own mailbox triggers the email, opens it and checks what it says.1 min read GuidesWebCheck forms and checkout after every WordPress plugin updatePlugin, 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.1 min read GuidesWebAdd functional checks to a website care planCare plans sell updates, backups and uptime. A nightly test that the form, booking or checkout still works is the check clients notice and understand.2 min read GuidesWebTest redirects after a site redesign or migrationOld addresses from Google and other sites must land on the right new page. A plain-language test opens each old URL and checks where it ends up and what the page says.2 min read GuidesiPhone and iPadAndroidTest a React Native app in plain English, without test IDsReact Native end-to-end suites are hard to set up and keep green. Write the journey in plain words, run it on iPhone and Android, and get a verdict with a replay.2 min read GuidesiPhone and iPadAndroidMobile tests that survive a redesignMobile end-to-end suites fail when screens change and the app still works. Why locator-based tests break, and how a test written as behaviour keeps passing.2 min read GuidesWebPaid, but still on the free plan: test the Stripe webhookStripe takes the money, the app never hears about it. A test that pays in test mode and checks the plan changed catches it.2 min read GuidesWebTest that a double click does not create two ordersA slow Pay button gets clicked twice and the customer is charged twice. Test what a hurried person does, then check exactly one order exists, not the thank-you page.2 min read GuidesWebTest that a multi-step form keeps answers when users go backStep 3 of a checkout or sign-up, the user presses Back to fix step 1 and finds every answer gone. One plain-language test goes back and forth and checks each value.2 min read GuidesWebRun tests in production without polluting your dataTests against production leave accounts, orders and sign-ups in your numbers. Mark test data so it is easy to filter and clean, and keep the runs that only read separate.2 min read GuidesWebTest both sides of a feature flag before you flip itA flag doubles the app you ship: on and off. Bugs hide in the side nobody tested. Two stored accounts, one in the rollout and one out, run the same journey each.2 min read GuidesWebUpgrade a framework without breaking what users doA major Next.js or React upgrade builds, passes type checks and still changes behaviour, like caching. Run your saved user journeys against the upgrade's preview first.2 min read GuidesWebTest a WooCommerce checkout after every updateWooCommerce, payment plugins and the theme update on their own schedules, and the checkout is where they collide. A nightly test places an order and checks it arrived.2 min read GuidesWebAfter moving a site to a new host, check the forms still sendThe pages look identical after a migration, but contact forms and password resets often stop sending email. Test the flows that leave the site, not just the pages.2 min read GuidesWebTest the phone menu on a client site after every updateThe hamburger menu is the navigation for most visitors, and it breaks after theme and plugin updates without anyone noticing on desktop. A phone-size test opens it.2 min read