<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Testsy blog</title>
<link>https://testsy.dev/blog/</link>
<description>Guides and engineering notes from the team building Testsy: how to check what your coding agent built, what we measured, and how the tester decides a verdict.</description>
<language>en</language>
<atom:link href="https://testsy.dev/blog/rss.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Testing an app you built with AI: a guide for founders</title>
<link>https://testsy.dev/blog/test-an-app-you-built-with-ai/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-an-app-you-built-with-ai/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<description>You built it with Claude Code, Cursor, Lovable or Bolt and it looks done. How to check it works for a stranger and keeps working after every change.</description>
</item>
<item>
<title>Find the bug before your client does: a guide for agencies</title>
<link>https://testsy.dev/blog/find-the-bug-before-your-client-does/</link>
<guid isPermaLink="true">https://testsy.dev/blog/find-the-bug-before-your-client-does/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Client sites</category>
<description>For agencies and freelancers: check client sites before handoff, keep checking after launch, test forms to the inbox and checkout after updates, and show the proof.</description>
</item>
<item>
<title>Release testing for product teams: a guide</title>
<link>https://testsy.dev/blog/release-testing-for-product-teams/</link>
<guid isPermaLink="true">https://testsy.dev/blog/release-testing-for-product-teams/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>CI, schedules and agents</category>
<description>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.</description>
</item>
<item>
<title>Mobile release testing: a guide for app teams</title>
<link>https://testsy.dev/blog/mobile-release-testing-for-app-teams/</link>
<guid isPermaLink="true">https://testsy.dev/blog/mobile-release-testing-for-app-teams/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Releases and regressions</category>
<description>For 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.</description>
</item>
<item>
<title>Your coding agent said “done”. Here is what it did not check</title>
<link>https://testsy.dev/blog/your-coding-agent-said-done-what-it-did-not-check/</link>
<guid isPermaLink="true">https://testsy.dev/blog/your-coding-agent-said-done-what-it-did-not-check/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>Verdicts and proof</category>
<description>Agents mark features complete after the code compiles and the unit tests pass. Why that misses broken screens, and how to check the feature as a user would.</description>
</item>
<item>
<title>Sign-up email links to localhost? Catch it before your users do</title>
<link>https://testsy.dev/blog/sign-up-email-links-to-localhost/</link>
<guid isPermaLink="true">https://testsy.dev/blog/sign-up-email-links-to-localhost/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>AI-built apps</category>
<category>Emails and messages</category>
<description>A confirmation or reset email that points at localhost or an old preview is a common bug in AI-built apps. A test that opens the real email finds it on the first run.</description>
</item>
<item>
<title>It works in preview and breaks in production. Test the live address</title>
<link>https://testsy.dev/blog/works-in-preview-broken-in-production/</link>
<guid isPermaLink="true">https://testsy.dev/blog/works-in-preview-broken-in-production/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>Releases and regressions</category>
<description>AI 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.</description>
</item>
<item>
<title>Fix one bug without breaking another: one bug, one test</title>
<link>https://testsy.dev/blog/fix-one-bug-without-breaking-another/</link>
<guid isPermaLink="true">https://testsy.dev/blog/fix-one-bug-without-breaking-another/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>Releases and regressions</category>
<description>AI-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.</description>
</item>
<item>
<title>Turn a failed test into a fix prompt for your coding agent</title>
<link>https://testsy.dev/blog/copy-the-fix-prompt-into-your-coding-agent/</link>
<guid isPermaLink="true">https://testsy.dev/blog/copy-the-fix-prompt-into-your-coding-agent/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>Verdicts and proof</category>
<description>Describing a bug to an AI agent is where fixes go wrong. Copy the fix prompt from a failed run instead: the check, what was seen, the steps and the proof.</description>
</item>
<item>
<title>Let Cursor check its own work in a real browser</title>
<link>https://testsy.dev/blog/let-cursor-check-its-own-work-in-a-browser/</link>
<guid isPermaLink="true">https://testsy.dev/blog/let-cursor-check-its-own-work-in-a-browser/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>CI, schedules and agents</category>
<description>Connect Testsy to Cursor over MCP so the agent can save a plain-language test, run it against your deployed app or a phone build, and read the verdict.</description>
</item>
<item>
<title>Let Codex check its own work in a real browser</title>
<link>https://testsy.dev/blog/let-codex-check-its-own-work-in-a-browser/</link>
<guid isPermaLink="true">https://testsy.dev/blog/let-codex-check-its-own-work-in-a-browser/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>CI, schedules and agents</category>
<description>Add Testsy to Codex with one command. The agent drafts a plain-language test, runs it against your app, reads every check and reruns after its fix.</description>
</item>
<item>
<title>Test from Gemini CLI, the Claude desktop app and claude.ai</title>
<link>https://testsy.dev/blog/connect-testsy-to-gemini-cli-and-the-claude-app/</link>
<guid isPermaLink="true">https://testsy.dev/blog/connect-testsy-to-gemini-cli-and-the-claude-app/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>CI, schedules and agents</category>
<description>Install Testsy as a Gemini CLI extension or a Claude connector, then ask in plain words for a browser or phone test and get a verdict with evidence.</description>
</item>
<item>
<title>Test a Lovable, Bolt or Replit app by its address, no code needed</title>
<link>https://testsy.dev/blog/test-a-lovable-bolt-or-replit-app-without-a-coding-agent/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-lovable-bolt-or-replit-app-without-a-coding-agent/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>AI-built apps</category>
<description>Built your app in Lovable, Bolt, Replit or v0? Paste the published address, describe a user's journey in plain words, and get a verdict with a replay.</description>
</item>
<item>
<title>Saved, then gone after a refresh: test that your app really saves</title>
<link>https://testsy.dev/blog/saved-then-gone-after-a-refresh/</link>
<guid isPermaLink="true">https://testsy.dev/blog/saved-then-gone-after-a-refresh/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Browser behaviour</category>
<category>AI-built apps</category>
<description>A screen can show data that was never stored. One plain-language test creates a record, reloads the page and checks it is still there, the bug AI-built apps ship most.</description>
</item>
<item>
<title>Test that one user cannot see another user's data</title>
<link>https://testsy.dev/blog/test-that-one-user-cannot-see-another-users-data/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-that-one-user-cannot-see-another-users-data/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>AI-built apps</category>
<description>Apps built with AI often show one account's records to another. A two-person test signs in as each, in separate browsers, and checks what each one can see.</description>
</item>
<item>
<title>Test password reset from the email to the new password</title>
<link>https://testsy.dev/blog/test-password-reset-from-the-email-to-the-new-password/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-password-reset-from-the-email-to-the-new-password/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>AI-built apps</category>
<category>Emails and messages</category>
<description>A reset email that links to the wrong host, or a link that fails in a new browser, locks users out. One test requests the reset, follows the link and signs in again.</description>
</item>
<item>
<title>Catch the blank white screen after a deploy</title>
<link>https://testsy.dev/blog/catch-a-blank-white-screen-after-deploy/</link>
<guid isPermaLink="true">https://testsy.dev/blog/catch-a-blank-white-screen-after-deploy/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Crashes and errors</category>
<category>AI-built apps</category>
<description>The most reported failure of AI-built apps is a page that renders nothing in production. A test that reads one value and records the console catches it on the first run.</description>
</item>
<item>
<title>Ten tests to run before you share your AI-built app</title>
<link>https://testsy.dev/blog/pre-launch-checklist-for-an-app-built-with-ai/</link>
<guid isPermaLink="true">https://testsy.dev/blog/pre-launch-checklist-for-an-app-built-with-ai/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>Releases and regressions</category>
<description>A 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.</description>
</item>
<item>
<title>Write a test without writing code: steps, checks and values</title>
<link>https://testsy.dev/blog/write-a-test-without-writing-code/</link>
<guid isPermaLink="true">https://testsy.dev/blog/write-a-test-without-writing-code/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>Verdicts and proof</category>
<description>A plain-language test is only as good as its checks. How to write steps a tester can follow and checks it can judge, with examples that pass review first time.</description>
</item>
<item>
<title>What an AI tester cannot check for you</title>
<link>https://testsy.dev/blog/what-an-ai-tester-cannot-check-for-you/</link>
<guid isPermaLink="true">https://testsy.dev/blog/what-an-ai-tester-cannot-check-for-you/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>Verdicts and proof</category>
<description>A browser test proves what a user can see and do. It does not audit security, load or code. An honest list of what Testsy covers, and what still needs a person.</description>
</item>
<item>
<title>Test every Vercel preview before you merge</title>
<link>https://testsy.dev/blog/test-every-vercel-preview-before-merge/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-every-vercel-preview-before-merge/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>CI, schedules and agents</category>
<description>Run your saved plain-language tests against each pull request's preview, including previews behind Vercel Deployment Protection, and fail on a regression.</description>
</item>
<item>
<title>Test Stripe checkout and plan upgrades in test mode</title>
<link>https://testsy.dev/blog/test-stripe-checkout-and-plan-upgrades/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-stripe-checkout-and-plan-upgrades/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>Releases and regressions</category>
<description>Billing 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.</description>
</item>
<item>
<title>Run browser tests after every deploy with GitHub Actions</title>
<link>https://testsy.dev/blog/run-browser-tests-after-every-deploy-with-github-actions/</link>
<guid isPermaLink="true">https://testsy.dev/blog/run-browser-tests-after-every-deploy-with-github-actions/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>CI, schedules and agents</category>
<description>A 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.</description>
</item>
<item>
<title>Tests that survive a redesign: why selector tests break</title>
<link>https://testsy.dev/blog/tests-that-survive-a-redesign/</link>
<guid isPermaLink="true">https://testsy.dev/blog/tests-that-survive-a-redesign/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>Choosing a tool</category>
<description>Test 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.</description>
</item>
<item>
<title>Check AI-written code before your customers do</title>
<link>https://testsy.dev/blog/check-ai-written-code-before-customers-do/</link>
<guid isPermaLink="true">https://testsy.dev/blog/check-ai-written-code-before-customers-do/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>Releases and regressions</category>
<description>Teams 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.</description>
</item>
<item>
<title>Run plain-language browser tests in GitLab CI</title>
<link>https://testsy.dev/blog/run-plain-language-tests-in-gitlab-ci/</link>
<guid isPermaLink="true">https://testsy.dev/blog/run-plain-language-tests-in-gitlab-ci/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>CI, schedules and agents</category>
<description>Include Testsy's GitLab template, point it at your project or a review app, and fail the pipeline on a broken journey, with JUnit results and watch links in the job.</description>
</item>
<item>
<title>Run browser tests from any CI with one file</title>
<link>https://testsy.dev/blog/run-browser-tests-from-any-ci-with-one-file/</link>
<guid isPermaLink="true">https://testsy.dev/blog/run-browser-tests-from-any-ci-with-one-file/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>CI, schedules and agents</category>
<description>CircleCI, Bitbucket, Jenkins, Buildkite or Azure Pipelines: one dependency-free script runs your saved tests, writes JUnit and exits non-zero on a failure.</description>
</item>
<item>
<title>Run your key journeys against production every night</title>
<link>https://testsy.dev/blog/run-tests-against-production-every-night/</link>
<guid isPermaLink="true">https://testsy.dev/blog/run-tests-against-production-every-night/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>CI, schedules and agents</category>
<description>Deploys 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.</description>
</item>
<item>
<title>Send test failures to Slack, with the proof attached</title>
<link>https://testsy.dev/blog/send-test-failures-to-slack/</link>
<guid isPermaLink="true">https://testsy.dev/blog/send-test-failures-to-slack/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sharing and alerts</category>
<category>CI, schedules and agents</category>
<description>Connect a Slack channel, subscribe it to the projects your team owns, and get failed, blocked and inconclusive runs with what was seen and a link to the replay.</description>
</item>
<item>
<title>Send test results to Linear or Jira with webhooks</title>
<link>https://testsy.dev/blog/send-test-results-to-linear-or-jira-with-webhooks/</link>
<guid isPermaLink="true">https://testsy.dev/blog/send-test-results-to-linear-or-jira-with-webhooks/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sharing and alerts</category>
<category>CI, schedules and agents</category>
<description>Testsy posts each finished run to your endpoint as signed JSON. Verify the signature, then open an issue with the failed check, what was seen and the link to the proof.</description>
</item>
<item>
<title>Test team invitations from the email to the joined workspace</title>
<link>https://testsy.dev/blog/test-team-invitations-by-email/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-team-invitations-by-email/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>Emails and messages</category>
<description>Invitations cross two people, two sessions and an email. One plain-language test invites a second address, accepts from the email and checks both sides see the same team.</description>
</item>
<item>
<title>Test admin and member roles: what each person can see and do</title>
<link>https://testsy.dev/blog/test-admin-and-member-roles/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-admin-and-member-roles/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>Releases and regressions</category>
<description>Permission 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.</description>
</item>
<item>
<title>Release checks for a startup with no QA team</title>
<link>https://testsy.dev/blog/release-checks-for-a-startup-with-no-qa-team/</link>
<guid isPermaLink="true">https://testsy.dev/blog/release-checks-for-a-startup-with-no-qa-team/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>CI, schedules and agents</category>
<description>No 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.</description>
</item>
<item>
<title>Flaky tests, and what a test verdict should be allowed to say</title>
<link>https://testsy.dev/blog/flaky-tests-and-what-a-verdict-should-say/</link>
<guid isPermaLink="true">https://testsy.dev/blog/flaky-tests-and-what-a-verdict-should-say/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>Verdicts and proof</category>
<description>A 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.</description>
</item>
<item>
<title>What a browser test suite costs when you pay per run</title>
<link>https://testsy.dev/blog/what-a-browser-test-suite-costs-per-run/</link>
<guid isPermaLink="true">https://testsy.dev/blog/what-a-browser-test-suite-costs-per-run/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>CI, schedules and agents</category>
<category>Choosing a tool</category>
<description>No seats and no minutes: one test run once is one run. How to estimate a month of release checks, schedules and CI runs on Testsy's plans, and what is never counted.</description>
</item>
<item>
<title>Test search, filters and sorting without hard-coding the data</title>
<link>https://testsy.dev/blog/test-search-filters-and-sorting/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-search-filters-and-sorting/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Hard interactions</category>
<category>Releases and regressions</category>
<description>Search 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.</description>
</item>
<item>
<title>Turn your release checklist into tests that run themselves</title>
<link>https://testsy.dev/blog/turn-a-release-checklist-into-saved-tests/</link>
<guid isPermaLink="true">https://testsy.dev/blog/turn-a-release-checklist-into-saved-tests/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>CI, schedules and agents</category>
<description>The 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.</description>
</item>
<item>
<title>Check the numbers: totals, prices and counts on screen</title>
<link>https://testsy.dev/blog/check-totals-prices-and-numbers-on-screen/</link>
<guid isPermaLink="true">https://testsy.dev/blog/check-totals-prices-and-numbers-on-screen/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>Verdicts and proof</category>
<description>A page that loads is not a page that is right. Make checks read the actual total, price or count, and keep the value the verdict was decided on as evidence.</description>
</item>
<item>
<title>Test receipts, notifications and other emails your app sends</title>
<link>https://testsy.dev/blog/test-receipts-and-notification-emails/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-receipts-and-notification-emails/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>Emails and messages</category>
<description>Order 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.</description>
</item>
<item>
<title>Share a live test run in a pull request, no account needed</title>
<link>https://testsy.dev/blog/share-a-live-test-run-in-a-pull-request/</link>
<guid isPermaLink="true">https://testsy.dev/blog/share-a-live-test-run-in-a-pull-request/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sharing and alerts</category>
<category>CI, schedules and agents</category>
<description>Every run started from CI, the API or an agent comes with a watch link. Paste it in the pull request and reviewers watch the browser live, then read the result.</description>
</item>
<item>
<title>A website launch QA checklist for agencies, with tests that run</title>
<link>https://testsy.dev/blog/website-launch-qa-checklist-for-agencies/</link>
<guid isPermaLink="true">https://testsy.dev/blog/website-launch-qa-checklist-for-agencies/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>Client sites</category>
<description>Forms, checkout, redirects, phone layouts and email: the launch checks agencies list every time, written as plain-language tests to run before handoff and after.</description>
</item>
<item>
<title>Test a contact form all the way to the inbox</title>
<link>https://testsy.dev/blog/test-a-contact-form-all-the-way-to-the-inbox/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-contact-form-all-the-way-to-the-inbox/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>Emails and messages</category>
<category>Client sites</category>
<description>“Message sent” on the page proves nothing. How to test that a form's confirmation email arrives and the submission reaches the owner, with a run that has its own mailbox.</description>
</item>
<item>
<title>Check forms and checkout after every WordPress plugin update</title>
<link>https://testsy.dev/blog/check-forms-after-every-wordpress-plugin-update/</link>
<guid isPermaLink="true">https://testsy.dev/blog/check-forms-after-every-wordpress-plugin-update/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>Client sites</category>
<description>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.</description>
</item>
<item>
<title>Test Shopify add to cart and checkout after an app or theme update</title>
<link>https://testsy.dev/blog/test-shopify-add-to-cart-and-checkout-after-an-app-update/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-shopify-add-to-cart-and-checkout-after-an-app-update/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>Client sites</category>
<description>An app install or theme update can silently break the cart. A plain-language test adds a variant, reaches checkout and pays with Shopify's test gateway, on a schedule.</description>
</item>
<item>
<title>Test a booking form or calendar embed from start to confirmation</title>
<link>https://testsy.dev/blog/test-a-booking-form-or-calendar-embed/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-booking-form-or-calendar-embed/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Browser behaviour</category>
<category>Forms and checkout</category>
<category>Client sites</category>
<description>Bookings run through date pickers, embedded widgets from another company and confirmation emails. One plain-language test books a slot and checks every step.</description>
</item>
<item>
<title>Show clients proof, not screenshots</title>
<link>https://testsy.dev/blog/show-clients-proof-not-screenshots/</link>
<guid isPermaLink="true">https://testsy.dev/blog/show-clients-proof-not-screenshots/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Client sites</category>
<category>Sharing and alerts</category>
<description>A screenshot in an email proves one moment. A share link to a test result shows each check, the value it saw, a replay and a video, and expires when you choose.</description>
</item>
<item>
<title>Organise testing for many client sites: one project per client</title>
<link>https://testsy.dev/blog/organise-client-sites-one-project-per-client/</link>
<guid isPermaLink="true">https://testsy.dev/blog/organise-client-sites-one-project-per-client/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Client sites</category>
<category>Sharing and alerts</category>
<description>How agencies keep tests, sign-in accounts, schedules and run usage separate per client, when to use a project and when a separate workspace with its own billing.</description>
</item>
<item>
<title>Add functional checks to a website care plan</title>
<link>https://testsy.dev/blog/add-functional-checks-to-a-website-care-plan/</link>
<guid isPermaLink="true">https://testsy.dev/blog/add-functional-checks-to-a-website-care-plan/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>Client sites</category>
<category>Sharing and alerts</category>
<description>Care plans sell updates, backups and uptime. A nightly test that the form, booking or checkout still works is the check clients notice and understand.</description>
</item>
<item>
<title>Test a site at phone, tablet and desktop sizes</title>
<link>https://testsy.dev/blog/test-a-site-at-phone-tablet-and-desktop-sizes/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-site-at-phone-tablet-and-desktop-sizes/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Devices and versions</category>
<category>Forms and checkout</category>
<category>Client sites</category>
<description>Most visitors arrive on a phone, and most QA happens on a laptop. Run the same plain-language test at 412 × 914, 820 × 1180 and 1280 × 800 and compare.</description>
</item>
<item>
<title>Test form validation messages, not only the happy path</title>
<link>https://testsy.dev/blog/test-form-validation-messages/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-form-validation-messages/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>Client sites</category>
<description>An empty or mistyped form should say what is wrong, where. A plain-language test submits it empty, reads the exact error, then completes it and reads the saved result.</description>
</item>
<item>
<title>Test redirects after a site redesign or migration</title>
<link>https://testsy.dev/blog/test-redirects-after-a-site-redesign/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-redirects-after-a-site-redesign/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>Client sites</category>
<description>Old 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.</description>
</item>
<item>
<title>Test a newsletter signup with double opt-in, end to end</title>
<link>https://testsy.dev/blog/test-a-newsletter-signup-double-opt-in/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-newsletter-signup-double-opt-in/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>Emails and messages</category>
<category>Client sites</category>
<description>A signup form that says “check your inbox” proves nothing until the confirmation email arrives and its link works. One test signs up, confirms and checks the welcome.</description>
</item>
<item>
<title>Test a cookie banner: accept, decline, and the choice sticking</title>
<link>https://testsy.dev/blog/test-a-cookie-banner-accept-and-decline/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-cookie-banner-accept-and-decline/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Browser behaviour</category>
<category>Client sites</category>
<description>Regulators expect rejecting cookies to be as easy as accepting them, and the choice to hold. A plain-language test clicks both, reloads, and checks the banner behaves.</description>
</item>
<item>
<title>A handoff record that proves the site worked at launch</title>
<link>https://testsy.dev/blog/a-handoff-record-that-proves-the-site-worked-at-launch/</link>
<guid isPermaLink="true">https://testsy.dev/blog/a-handoff-record-that-proves-the-site-worked-at-launch/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Client sites</category>
<category>Sharing and alerts</category>
<description>Scope arguments after launch start with “it never worked”. Run the key journeys at handoff and keep the results, with replays, as the record both sides can open.</description>
</item>
<item>
<title>Give clients a viewer seat to see their test results</title>
<link>https://testsy.dev/blog/give-clients-a-viewer-seat-to-see-test-results/</link>
<guid isPermaLink="true">https://testsy.dev/blog/give-clients-a-viewer-seat-to-see-test-results/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Client sites</category>
<category>Sharing and alerts</category>
<description>A viewer sees projects, tests, runs and the proof, and changes nothing. When to invite a client as a viewer, when a share link is enough, and when to split workspaces.</description>
</item>
<item>
<title>When bot protection blocks your tests, and how to allow them</title>
<link>https://testsy.dev/blog/when-bot-protection-blocks-your-tests/</link>
<guid isPermaLink="true">https://testsy.dev/blog/when-bot-protection-blocks-your-tests/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Browser behaviour</category>
<category>Client sites</category>
<description>Cloudflare-style challenges and firewalls stop automated browsers, including the tester. Why a blocked run is not counted, and how to allow Testsy's static addresses.</description>
</item>
<item>
<title>Test a multilingual site and its language switcher</title>
<link>https://testsy.dev/blog/test-a-multilingual-site-and-its-language-switcher/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-multilingual-site-and-its-language-switcher/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Browser behaviour</category>
<category>Client sites</category>
<description>The switcher sends French visitors to an English page, or loses the page on switch. Test each language version, and browse from the country you need.</description>
</item>
<item>
<title>Pass App Store review: test what the reviewer will do first</title>
<link>https://testsy.dev/blog/pass-app-store-review-test-what-the-reviewer-will-do/</link>
<guid isPermaLink="true">https://testsy.dev/blog/pass-app-store-review-test-what-the-reviewer-will-do/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Sign-in and codes</category>
<category>Crashes and errors</category>
<category>App builds and review</category>
<description>Apple says over 40% of unresolved review issues fall under guideline 2.1. Test the reviewer's path: install, sign in with the demo account, reach the content.</description>
</item>
<item>
<title>Test an Expo app in CI without rebuilding it every time</title>
<link>https://testsy.dev/blog/test-an-expo-app-in-ci-without-rebuilding-every-time/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-an-expo-app-in-ci-without-rebuilding-every-time/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>App builds and review</category>
<category>CI, schedules and agents</category>
<description>Native builds are the slow part of mobile CI. Store an Expo fingerprint with each build, skip the build when it has not changed, and test the one you have.</description>
</item>
<item>
<title>Build an Android APK that runs on cloud test devices</title>
<link>https://testsy.dev/blog/build-an-android-apk-that-runs-on-test-devices/</link>
<guid isPermaLink="true">https://testsy.dev/blog/build-an-android-apk-that-runs-on-test-devices/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Android</category>
<category>App builds and review</category>
<category>CI, schedules and agents</category>
<description>Why an APK needs both arm64-v8a and x86_64 native code to run on Android emulators, and the exact build command for React Native, Expo, Flutter and Gradle.</description>
</item>
<item>
<title>Build an iOS app for cloud testing: a zipped Simulator .app</title>
<link>https://testsy.dev/blog/build-an-ios-app-for-testing/</link>
<guid isPermaLink="true">https://testsy.dev/blog/build-an-ios-app-for-testing/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>App builds and review</category>
<category>CI, schedules and agents</category>
<description>Testsy runs iPhone and iPad tests on an iOS Simulator build. The xcodebuild, Expo and Flutter commands that make one, how to zip it, and what to do in CI.</description>
</item>
<item>
<title>Test a React Native app in plain English, without test IDs</title>
<link>https://testsy.dev/blog/test-a-react-native-app-in-plain-english/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-react-native-app-in-plain-english/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Releases and regressions</category>
<description>React 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.</description>
</item>
<item>
<title>Test a Flutter app on iPhone and Android, canvas included</title>
<link>https://testsy.dev/blog/test-a-flutter-app-on-iphone-and-android/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-flutter-app-on-iphone-and-android/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Hard interactions</category>
<description>Flutter draws its own widgets, which trips up tools that read the native view tree. How Testsy tests Flutter apps, the iOS build to upload, and drawn content.</description>
</item>
<item>
<title>Test mobile onboarding and the first launch, on a fresh install</title>
<link>https://testsy.dev/blog/test-mobile-onboarding-and-first-launch/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-mobile-onboarding-and-first-launch/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Prompts and permissions</category>
<description>First launch is where new users decide. Each app run starts with fresh app data, so onboarding, prompts and the empty state are tested as a new user sees them.</description>
</item>
<item>
<title>Test your app's iPad layout and landscape, not only the phone</title>
<link>https://testsy.dev/blog/test-an-ipad-layout-and-landscape/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-an-ipad-layout-and-landscape/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Devices and versions</category>
<description>Apps built and tested on an iPhone break on an iPad or turned sideways. Run the same test on a tablet and in landscape, and check the layout-specific parts.</description>
</item>
<item>
<title>One test for iPhone and Android: write it once, run it on both</title>
<link>https://testsy.dev/blog/one-test-for-iphone-and-android/</link>
<guid isPermaLink="true">https://testsy.dev/blog/one-test-for-iphone-and-android/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Devices and versions</category>
<description>The same plain-language test runs on an iOS build and an Android build. Where the two platforms differ, how to word a test for both, and what each result shows.</description>
</item>
<item>
<title>Test a chat or marketplace app with two phones in one test</title>
<link>https://testsy.dev/blog/test-a-chat-or-marketplace-app-with-two-phones/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-chat-or-marketplace-app-with-two-phones/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Devices and versions</category>
<description>Messages, offers, invitations and live updates need two people on two devices. One test can use two phones, and say what each person does and sees.</description>
</item>
<item>
<title>Let your coding agent test the mobile app it just built</title>
<link>https://testsy.dev/blog/let-your-coding-agent-test-the-mobile-app-it-built/</link>
<guid isPermaLink="true">https://testsy.dev/blog/let-your-coding-agent-test-the-mobile-app-it-built/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>AI-built apps</category>
<category>CI, schedules and agents</category>
<description>Claude Code, Cursor or Codex builds the app, uploads the build over MCP without an API key in the shell, runs your saved app tests and reads the verdict.</description>
</item>
<item>
<title>Mobile tests that survive a redesign</title>
<link>https://testsy.dev/blog/mobile-tests-that-survive-a-redesign/</link>
<guid isPermaLink="true">https://testsy.dev/blog/mobile-tests-that-survive-a-redesign/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Releases and regressions</category>
<description>Mobile 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.</description>
</item>
<item>
<title>Sign in to a mobile app in a test without the password in the test</title>
<link>https://testsy.dev/blog/sign-in-to-a-mobile-app-with-a-stored-account/</link>
<guid isPermaLink="true">https://testsy.dev/blog/sign-in-to-a-mobile-app-with-a-stored-account/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Sign-in and codes</category>
<description>Most app tests start behind a sign-in. Store the account once; the tester types the password into the app itself and the AI never sees it, on iPhone and Android.</description>
</item>
<item>
<title>Import app builds from EAS, Bitrise or S3 by link</title>
<link>https://testsy.dev/blog/import-app-builds-from-eas-bitrise-or-s3/</link>
<guid isPermaLink="true">https://testsy.dev/blog/import-app-builds-from-eas-bitrise-or-s3/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>App builds and review</category>
<category>CI, schedules and agents</category>
<description>If your pipeline already stores the APK or zipped .app somewhere, give Testsy the link. It fetches the build, checks it and runs the app's tests, with no upload step.</description>
</item>
<item>
<title>Test a Capacitor or Ionic app: native shell, web content</title>
<link>https://testsy.dev/blog/test-a-capacitor-or-ionic-app/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-capacitor-or-ionic-app/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Browser behaviour</category>
<description>Capacitor and Ionic apps are web pages inside a native shell. How the tester works in the web view, the build to upload, and why a debug build gives more detail.</description>
</item>
<item>
<title>Sign-up emails that stop arriving after launch</title>
<link>https://testsy.dev/blog/sign-up-emails-stopped-arriving-after-launch/</link>
<guid isPermaLink="true">https://testsy.dev/blog/sign-up-emails-stopped-arriving-after-launch/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>AI-built apps</category>
<category>Emails and messages</category>
<description>Supabase's built-in mailer sends 2 emails an hour, only to your own team. Sign-up works for you and fails for everyone else. A test with its own mailbox catches it.</description>
</item>
<item>
<title>Paid, but still on the free plan: test the Stripe webhook</title>
<link>https://testsy.dev/blog/paid-but-still-on-the-free-plan/</link>
<guid isPermaLink="true">https://testsy.dev/blog/paid-but-still-on-the-free-plan/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>AI-built apps</category>
<category>Releases and regressions</category>
<description>Stripe takes the money, the app never hears about it. A test that pays in test mode and checks the plan changed catches it.</description>
</item>
<item>
<title>Uploads that work for you and fail for your users</title>
<link>https://testsy.dev/blog/uploads-work-for-you-fail-for-your-users/</link>
<guid isPermaLink="true">https://testsy.dev/blog/uploads-work-for-you-fail-for-your-users/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>Files and media</category>
<category>AI-built apps</category>
<description>A photo upload works when you try it and fails for a normal user with a 403 from storage rules. Test it as a normal account, with a real file, and check after a reload.</description>
</item>
<item>
<title>Test your app as a brand-new user, not as yourself</title>
<link>https://testsy.dev/blog/test-your-app-as-a-brand-new-user/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-your-app-as-a-brand-new-user/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>AI-built apps</category>
<category>Emails and messages</category>
<description>Your account has data, a team and every flag on. A new user's has nothing. Sign up fresh on every run and check the first thing a new user must be able to create.</description>
</item>
<item>
<title>Test that a double click does not create two orders</title>
<link>https://testsy.dev/blog/stop-double-clicks-creating-duplicate-orders/</link>
<guid isPermaLink="true">https://testsy.dev/blog/stop-double-clicks-creating-duplicate-orders/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Hard interactions</category>
<category>Forms and checkout</category>
<category>Releases and regressions</category>
<description>A 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.</description>
</item>
<item>
<title>Test that a multi-step form keeps answers when users go back</title>
<link>https://testsy.dev/blog/multi-step-forms-that-lose-answers-on-back/</link>
<guid isPermaLink="true">https://testsy.dev/blog/multi-step-forms-that-lose-answers-on-back/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>Releases and regressions</category>
<description>Step 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.</description>
</item>
<item>
<title>Run tests in production without polluting your data</title>
<link>https://testsy.dev/blog/run-tests-in-production-without-polluting-your-data/</link>
<guid isPermaLink="true">https://testsy.dev/blog/run-tests-in-production-without-polluting-your-data/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>CI, schedules and agents</category>
<description>Tests 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.</description>
</item>
<item>
<title>Test both sides of a feature flag before you flip it</title>
<link>https://testsy.dev/blog/test-both-sides-of-a-feature-flag/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-both-sides-of-a-feature-flag/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>Releases and regressions</category>
<category>CI, schedules and agents</category>
<description>A 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.</description>
</item>
<item>
<title>Upgrade a framework without breaking what users do</title>
<link>https://testsy.dev/blog/upgrade-a-framework-without-breaking-user-flows/</link>
<guid isPermaLink="true">https://testsy.dev/blog/upgrade-a-framework-without-breaking-user-flows/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>CI, schedules and agents</category>
<description>A 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.</description>
</item>
<item>
<title>Write tests in your team's own language</title>
<link>https://testsy.dev/blog/write-tests-in-your-teams-own-language/</link>
<guid isPermaLink="true">https://testsy.dev/blog/write-tests-in-your-teams-own-language/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>Verdicts and proof</category>
<description>Tests in Spanish, Vietnamese or German, with the plan and results in that language and the screen's text kept as it is. Two real runs, and the lesson one of them taught.</description>
</item>
<item>
<title>Check the record was saved, not just the success message</title>
<link>https://testsy.dev/blog/check-the-database-not-just-the-success-message/</link>
<guid isPermaLink="true">https://testsy.dev/blog/check-the-database-not-just-the-success-message/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>CI, schedules and agents</category>
<description>A thank-you message proves the page changed, not that anything was stored. Check the record on screen, or read your system through an endpoint you define.</description>
</item>
<item>
<title>Test a WooCommerce checkout after every update</title>
<link>https://testsy.dev/blog/test-woocommerce-checkout-after-every-update/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-woocommerce-checkout-after-every-update/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>Releases and regressions</category>
<category>Client sites</category>
<description>WooCommerce, 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.</description>
</item>
<item>
<title>After moving a site to a new host, check the forms still send</title>
<link>https://testsy.dev/blog/after-moving-hosts-check-the-forms-still-send/</link>
<guid isPermaLink="true">https://testsy.dev/blog/after-moving-hosts-check-the-forms-still-send/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Releases and regressions</category>
<category>Emails and messages</category>
<category>Client sites</category>
<description>The 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.</description>
</item>
<item>
<title>Test what visitors in another country see</title>
<link>https://testsy.dev/blog/test-what-visitors-in-another-country-see/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-what-visitors-in-another-country-see/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Browser behaviour</category>
<category>Client sites</category>
<description>Prices in the wrong currency, a missing EU cookie banner, a redirect to the wrong store. Tests can browse from the client's country, with its time zone and language.</description>
</item>
<item>
<title>Test a lead magnet from the form to the inbox to the file</title>
<link>https://testsy.dev/blog/test-a-lead-magnet-from-form-to-inbox-to-file/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-lead-magnet-from-form-to-inbox-to-file/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Files and media</category>
<category>Emails and messages</category>
<category>Client sites</category>
<description>A free guide behind a form is three systems: the form, the email tool and the file. Any of them can break unseen. One test signs up, opens the email and checks the file.</description>
</item>
<item>
<title>Test a membership site: members in, everyone else out</title>
<link>https://testsy.dev/blog/test-a-membership-site-members-in-everyone-else-out/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-membership-site-members-in-everyone-else-out/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>Client sites</category>
<description>Caching can show members' content to the public, or lock members out. One test signs in as a member and checks a visitor in a separate browser sees only the teaser.</description>
</item>
<item>
<title>What survives when a user deletes and reinstalls your app</title>
<link>https://testsy.dev/blog/what-survives-when-a-user-reinstalls-your-app/</link>
<guid isPermaLink="true">https://testsy.dev/blog/what-survives-when-a-user-reinstalls-your-app/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Sign-in and codes</category>
<category>Phone state</category>
<description>On iPhone, deleting an app clears its files but not its keychain, so a reinstall can come back signed in. A real run shows the note wiped and the token still there.</description>
</item>
<item>
<title>Find unlabeled buttons and tiny tap targets in a mobile app</title>
<link>https://testsy.dev/blog/find-unlabeled-buttons-and-tiny-tap-targets-in-a-mobile-app/</link>
<guid isPermaLink="true">https://testsy.dev/blog/find-unlabeled-buttons-and-tiny-tap-targets-in-a-mobile-app/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Devices and versions</category>
<category>App builds and review</category>
<description>Apple's App Store now shows accessibility labels on product pages. An audit run on an iPhone, inside a normal test, catches low contrast, missing labels, small targets.</description>
</item>
<item>
<title>Test the Android Back button after the Android 16 change</title>
<link>https://testsy.dev/blog/test-the-android-back-button-and-back-gesture/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-the-android-back-button-and-back-gesture/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Android</category>
<category>Phone state</category>
<category>Hard interactions</category>
<category>App builds and review</category>
<description>Apps targeting Android 16 no longer get onBackPressed, and Google Play requires that target. A real run tests the Back button, a cancelled back gesture and split screen.</description>
</item>
<item>
<title>The keyboard covers the text field on Android 15 and 16</title>
<link>https://testsy.dev/blog/the-keyboard-covers-the-text-field-on-android/</link>
<guid isPermaLink="true">https://testsy.dev/blog/the-keyboard-covers-the-text-field-on-android/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Android</category>
<category>Hard interactions</category>
<category>Forms and checkout</category>
<description>Apps targeting Android 15 draw edge to edge and the window no longer resizes for the keyboard, so fields end up behind it. A real run checks the field stays visible.</description>
</item>
<item>
<title>Test what users see when a request fails</title>
<link>https://testsy.dev/blog/test-what-users-see-when-a-request-fails/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-what-users-see-when-a-request-fails/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Slow and failing pages</category>
<category>AI-built apps</category>
<description>Apps built with AI handle the happy path and show a blank page or a spinner forever when an API fails. Test the error message, the Retry button and the slow case.</description>
</item>
<item>
<title>Sign in with Google works locally and fails in production</title>
<link>https://testsy.dev/blog/sign-in-with-google-works-locally-fails-in-production/</link>
<guid isPermaLink="true">https://testsy.dev/blog/sign-in-with-google-works-locally-fails-in-production/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>AI-built apps</category>
<description>“Error 400: redirect_uri_mismatch” is what new users see when the Google sign-in was only set up for localhost. A test presses the button and checks where it lands.</description>
</item>
<item>
<title>Test gestures in a mobile app: long press, swipe, drag and pinch</title>
<link>https://testsy.dev/blog/test-gestures-in-a-mobile-app/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-gestures-in-a-mobile-app/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Hard interactions</category>
<description>Gestures are where mobile UI tests are weakest and where gesture libraries clash. A real iPhone run does long press, swipes, drag to reorder, pinch and rotate.</description>
</item>
<item>
<title>Test a long list on Android: scroll, swipe to delete, pull to refresh</title>
<link>https://testsy.dev/blog/test-a-long-list-swipe-to-delete-and-pull-to-refresh/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-long-list-swipe-to-delete-and-pull-to-refresh/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Android</category>
<category>Hard interactions</category>
<description>Lists are where scrolling, swipe actions and pull to refresh compete for the same finger. A real Android run scrolls to item 75, swipes one away and refreshes.</description>
</item>
<item>
<title>“Coupon applied” is not a discount: test the total, not the message</title>
<link>https://testsy.dev/blog/test-a-coupon-applied-is-not-discounted/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-coupon-applied-is-not-discounted/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Android</category>
<category>Forms and checkout</category>
<category>Verdicts and proof</category>
<description>An app says the coupon was applied and charges full price. A real Android run caught exactly that, because the check was on the subtotal, not on the message.</description>
</item>
<item>
<title>Test photo and file pickers in a mobile app</title>
<link>https://testsy.dev/blog/test-photo-and-file-pickers-in-a-mobile-app/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-photo-and-file-pickers-in-a-mobile-app/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Prompts and permissions</category>
<category>Files and media</category>
<description>Picking a photo or a file runs through the phone's own screens, which app tests rarely reach. A real iPhone run picks a photo, a PDF, and a PDF where an image belongs.</description>
</item>
<item>
<title>Test the phone menu on a client site after every update</title>
<link>https://testsy.dev/blog/test-the-mobile-menu-on-a-client-site/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-the-mobile-menu-on-a-client-site/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Devices and versions</category>
<category>Releases and regressions</category>
<category>Client sites</category>
<description>The 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.</description>
</item>
<item>
<title>Test the files your mobile app exports, downloads and shares</title>
<link>https://testsy.dev/blog/test-files-your-mobile-app-exports-and-shares/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-files-your-mobile-app-exports-and-shares/</guid>
<pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Android</category>
<category>Prompts and permissions</category>
<category>Files and media</category>
<description>“Export complete” proves nothing about the file. A real Android run opens the CSV the app wrote, checks its rows, shares it through the share sheet and reads a download.</description>
</item>
<item>
<title>The hardest parts of web testing, each one run for real</title>
<link>https://testsy.dev/blog/the-hardest-parts-of-web-testing/</link>
<guid isPermaLink="true">https://testsy.dev/blog/the-hardest-parts-of-web-testing/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<description>Iframes, new tabs, downloads, uploads, drag and drop, slow pages, video, email codes, two sites at once. Why each is hard to automate, and a real run of each.</description>
</item>
<item>
<title>Test a form inside an iframe, Shadow DOM and a new tab</title>
<link>https://testsy.dev/blog/test-iframes-shadow-dom-and-new-tabs/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-iframes-shadow-dom-and-new-tabs/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Browser behaviour</category>
<description>Three places a page hides its controls from a test script. One plain-language test fills a form in an iframe, clicks inside Shadow DOM and follows a link into a new tab.</description>
</item>
<item>
<title>Test what is inside a download: CSV, Excel, PDF and ZIP</title>
<link>https://testsy.dev/blog/test-what-is-inside-a-downloaded-file/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-what-is-inside-a-downloaded-file/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Files and media</category>
<description>A file that arrives is not a file that is right. Two plain-language tests download five files, open each one and compare what is inside with what the page shows.</description>
</item>
<item>
<title>Test file uploads: a good file, a fake one and one too big</title>
<link>https://testsy.dev/blog/test-file-uploads-good-fake-and-too-big/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-file-uploads-good-fake-and-too-big/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Files and media</category>
<description>Upload tests need a folder of awkward files nobody keeps. Two plain-language tests upload a photo, a text file named .jpg, a 52 MB image, two CSVs and two documents.</description>
</item>
<item>
<title>Test drag and drop, resizing and drawing on a canvas</title>
<link>https://testsy.dev/blog/test-drag-and-drop-resize-and-canvas/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-drag-and-drop-resize-and-canvas/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Hard interactions</category>
<description>Dragging is a gesture, not a click, and a canvas has nothing inside it to select. One plain-language test drags, reorders, resizes and draws, and reads each result.</description>
</item>
<item>
<title>Test alert, confirm and prompt, and the browser's permission prompts</title>
<link>https://testsy.dev/blog/test-browser-dialogs-and-permission-prompts/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-browser-dialogs-and-permission-prompts/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Prompts and permissions</category>
<category>Browser behaviour</category>
<description>These boxes belong to the browser, not the page, and they stop everything until answered. One plain-language test accepts, cancels, types an answer, allows and blocks.</description>
</item>
<item>
<title>Test that sign-in and saved data survive a reload</title>
<link>https://testsy.dev/blog/test-that-sign-in-survives-a-reload/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-that-sign-in-survives-a-reload/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>Browser behaviour</category>
<description>The page looked right until someone pressed refresh. One plain-language test signs in, reloads, saves a note, reloads again and checks what is left.</description>
</item>
<item>
<title>Test slow pages and failed requests without a single sleep</title>
<link>https://testsy.dev/blog/test-slow-pages-without-sleeps/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-slow-pages-without-sleeps/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Slow and failing pages</category>
<category>Verdicts and proof</category>
<description>A button that is not ready, a report still loading, a request that fails, a page that never finishes. Three plain-language tests with no wait times in them.</description>
</item>
<item>
<title>One web test across a frame, an upload, a second tab and a download</title>
<link>https://testsy.dev/blog/test-a-workflow-across-tabs-uploads-and-downloads/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-a-workflow-across-tabs-uploads-and-downloads/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Files and media</category>
<category>Browser behaviour</category>
<description>Real workflows cross every boundary a script hates in one sitting. One test uploads a file in a sandboxed frame, approves in another tab and reads the manifest.</description>
</item>
<item>
<title>Test that a video really plays, and what the page says when it cannot</title>
<link>https://testsy.dev/blog/test-that-a-video-really-plays/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-that-a-video-really-plays/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Files and media</category>
<description>A player on the page is not a video that plays. One plain-language test presses play, checks the time moves, checks captions, plays audio and finds a broken video.</description>
</item>
<item>
<title>Test date pickers, hover, right-click menus and keyboard shortcuts</title>
<link>https://testsy.dev/blog/test-date-pickers-menus-and-keyboard-shortcuts/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-date-pickers-menus-and-keyboard-shortcuts/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Hard interactions</category>
<description>Custom widgets are where plain form tests stop. Two plain-language tests sort a table, pick dates two ways, format text, hover, right-click and use the keyboard.</description>
</item>
<item>
<title>Test email verification codes, the wrong code and the resend too</title>
<link>https://testsy.dev/blog/test-email-verification-codes-wrong-code-and-resend/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-email-verification-codes-wrong-code-and-resend/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>Forms and checkout</category>
<description>A sign-up test that stops at "we sent you a code" proves little. Two real runs read the email, try a wrong code, ask for a new one and finish signing up.</description>
</item>
<item>
<title>Test an admin site and a public site, as two people, in one test</title>
<link>https://testsy.dev/blog/test-an-admin-site-and-a-public-site-as-two-people/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-an-admin-site-and-a-public-site-as-two-people/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<category>Browser behaviour</category>
<description>What an editor publishes, a visitor must see, and a draft must stay hidden. Two real runs cross from an admin site to a public one, in two separate browsers.</description>
</item>
<item>
<title>The hardest parts of mobile app testing, each one run for real</title>
<link>https://testsy.dev/blog/the-hardest-parts-of-mobile-app-testing/</link>
<guid isPermaLink="true">https://testsy.dev/blog/the-hardest-parts-of-mobile-app-testing/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<description>Permission prompts, notifications, SMS codes, Face ID, location, crashes, old OS versions. Why each is hard to test, and a real run of each with its result and video.</description>
</item>
<item>
<title>Test that a notification opens the right screen</title>
<link>https://testsy.dev/blog/test-that-a-notification-opens-the-right-screen/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-that-a-notification-opens-the-right-screen/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Notifications and links</category>
<description>The notification arrived. Did tapping it open the order, or only the home screen? A plain-language test waits for it, taps it and checks where the app lands.</description>
</item>
<item>
<title>Test what your app does when the user says no to a permission</title>
<link>https://testsy.dev/blog/test-permission-prompts-in-a-mobile-app/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-permission-prompts-in-a-mobile-app/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Prompts and permissions</category>
<description>Location allowed, camera denied, microphone denied, contacts allowed. One plain-language test answers each system prompt as told and checks what the app shows after.</description>
</item>
<item>
<title>Test SMS code sign-in on Android without a second phone</title>
<link>https://testsy.dev/blog/test-sms-code-sign-in-on-android/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-sms-code-sign-in-on-android/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Android</category>
<category>Sign-in and codes</category>
<description>A text message arrives, Android offers the code, the app verifies it. One plain-language test covers the whole hand-off, with the message and the result on video.</description>
</item>
<item>
<title>Test deep links: does the link open the right screen?</title>
<link>https://testsy.dev/blog/test-deep-links-in-a-mobile-app/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-deep-links-in-a-mobile-app/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Notifications and links</category>
<description>A link in an email or an ad should land on the item, not the home screen. A plain-language test opens the link on the phone and checks the screen the app shows.</description>
</item>
<item>
<title>Test Face ID unlock: the wrong face, then the right one</title>
<link>https://testsy.dev/blog/test-face-id-and-fingerprint-unlock/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-face-id-and-fingerprint-unlock/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Sign-in and codes</category>
<category>Prompts and permissions</category>
<description>The locked path matters as much as the unlocked one. A plain-language test answers the Face ID prompt with the wrong face, then the right one, and checks both.</description>
</item>
<item>
<title>Test what your app remembers after the phone kills it</title>
<link>https://testsy.dev/blog/test-app-state-after-the-phone-kills-it/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-app-state-after-the-phone-kills-it/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Phone state</category>
<description>Phones close apps in the background to free memory. A plain-language test types a draft, has the phone kill the app, reopens it and checks the draft is still there.</description>
</item>
<item>
<title>A mobile app crash, caught with the file and line that caused it</title>
<link>https://testsy.dev/blog/catch-a-mobile-app-crash-with-its-stack-trace/</link>
<guid isPermaLink="true">https://testsy.dev/blog/catch-a-mobile-app-crash-with-its-stack-trace/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Crashes and errors</category>
<description>We asked for an order confirmation. The app crashed instead. The result names the error, the step it came after, the stack trace and the steps to reproduce it.</description>
</item>
<item>
<title>Test your app offline, on low battery and during a phone call</title>
<link>https://testsy.dev/blog/test-offline-low-battery-and-incoming-calls/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-offline-low-battery-and-incoming-calls/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Android</category>
<category>Phone state</category>
<description>A phone loses signal, runs low and rings. Two plain-language tests on Android switch the network off and on, set the battery to 15% and take an incoming call.</description>
</item>
<item>
<title>Test rotation, dark mode and the largest text size</title>
<link>https://testsy.dev/blog/test-rotation-dark-mode-and-large-text/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-rotation-dark-mode-and-large-text/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Phone state</category>
<category>Devices and versions</category>
<description>Three phone settings change every screen in your app at once. Two plain-language tests flip each one mid-run and check that the app still reads and still works.</description>
</item>
<item>
<title>Test location features without leaving your desk</title>
<link>https://testsy.dev/blog/test-location-features-in-a-mobile-app/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-location-features-in-a-mobile-app/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Phone state</category>
<category>Verdicts and proof</category>
<description>Set where the phone is, move it along a route at walking or driving speed, and check what your app shows. Two real runs, and one passing check that hid a bug.</description>
</item>
<item>
<title>Test a Live Activity and a home-screen widget on iPhone</title>
<link>https://testsy.dev/blog/test-live-activities-and-home-screen-widgets/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-live-activities-and-home-screen-widgets/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Notifications and links</category>
<description>They are your app, shown where your app is not: the lock screen, the Dynamic Island, the home screen. One plain-language test starts one, adds the other and reads both.</description>
</item>
<item>
<title>One mobile test, six OS versions: what changed on screen</title>
<link>https://testsy.dev/blog/one-mobile-test-on-every-os-version/</link>
<guid isPermaLink="true">https://testsy.dev/blog/one-mobile-test-on-every-os-version/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>iPhone and iPad</category>
<category>Android</category>
<category>Prompts and permissions</category>
<category>Devices and versions</category>
<description>We ran the same plain-language tests on iOS 17, 18 and 27 and on Android 10, 12 and 16. The prompts differed on every version. The test text never changed.</description>
</item>
<item>
<title>Moving from TesterArmy to Testsy before 15 January</title>
<link>https://testsy.dev/blog/moving-from-testerarmy-to-testsy/</link>
<guid isPermaLink="true">https://testsy.dev/blog/moving-from-testerarmy-to-testsy/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Migration</category>
<category>Choosing a tool</category>
<description>TesterArmy's dashboard closes after 15 January 2027. Here is what carries over to Testsy, what does not, and how to move a plain-English test suite.</description>
</item>
<item>
<title>Making an AI tester prove its verdicts</title>
<link>https://testsy.dev/blog/making-an-ai-tester-prove-its-verdicts/</link>
<guid isPermaLink="true">https://testsy.dev/blog/making-an-ai-tester-prove-its-verdicts/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Engineering</category>
<category>Web</category>
<category>Files and media</category>
<category>Verdicts and proof</category>
<description>An agent that drives a browser can say "passed" about almost anything. These are the rules we built Testsy on so that every verdict comes with its evidence.</description>
</item>
<item>
<title>Make Claude Code test what it just built</title>
<link>https://testsy.dev/blog/make-claude-code-test-what-it-built/</link>
<guid isPermaLink="true">https://testsy.dev/blog/make-claude-code-test-what-it-built/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>CI, schedules and agents</category>
<description>Your coding agent says the feature works. Connect Testsy over MCP and it has to run the feature in a real browser and bring back proof before it says done.</description>
</item>
<item>
<title>Test sign-ups that send an email or SMS code</title>
<link>https://testsy.dev/blog/test-sign-ups-that-send-an-email-or-sms-code/</link>
<guid isPermaLink="true">https://testsy.dev/blog/test-sign-ups-that-send-an-email-or-sms-code/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Sign-in and codes</category>
<description>A sign-up form that submits is not a sign-up that works. Give the test its own mailbox or phone number and check the whole journey, code included.</description>
</item>
<item>
<title>A daily check on every client site's key flow</title>
<link>https://testsy.dev/blog/a-daily-check-for-every-client-site/</link>
<guid isPermaLink="true">https://testsy.dev/blog/a-daily-check-for-every-client-site/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Guides</category>
<category>Web</category>
<category>Forms and checkout</category>
<category>CI, schedules and agents</category>
<description>Clients find out their booking form is broken from their customers. Set up one scheduled test per site, get told when it fails, and send the client the proof.</description>
</item>
<item>
<title>Five AI testers, one planted bug: what each verdict rested on</title>
<link>https://testsy.dev/blog/five-ai-testers-one-planted-bug/</link>
<guid isPermaLink="true">https://testsy.dev/blog/five-ai-testers-one-planted-bug/</guid>
<pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
<category>Comparisons</category>
<category>Web</category>
<category>Files and media</category>
<category>Verdicts and proof</category>
<category>Choosing a tool</category>
<description>We gave the same tests to five AI testing tools and to our own, one with a bug planted in a download. One tool passed it and one excused it. Here is what we saw.</description>
</item>
</channel>
</rss>
