BLOG
BlogGuides

Release testing for product teams: a guide

Check 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.

The job#

Your team ships often, more of the code is written by AI, and nobody has time to click through the product before each release. Google's 2025 DORA report found that AI adoption continues to have a negative relationship with software delivery stability. The work of catching what broke has to happen somewhere, and it is cheapest right after the deploy, before customers find it.

These posts describe how to do that with plain-language tests that run in a real browser (and on iPhone and Android for apps), with proof for every check.

Decide what to test#

Run them on every change#

Test the journeys that matter#

Hear about it, and share it#

Keep it trustworthy#

The hard parts of the web (iframes, downloads, uploads, drag and drop, slow pages) have their own series with a real run for each: The hardest parts of web testing, each one run for real.

Start this week#

Write the three tests whose failure would hurt most, run them from the app until they pass, then add them to your pipeline. The free trial has 10 runs and needs no card.

Filed underWebReleases and regressionsCI, schedules and agents