BlogTopic
Tests in CI, on a schedule and from a coding agent
Running the tests without a person: from a pipeline, every morning, or by the coding agent that wrote the change.
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
GuidesWebLet Cursor check its own work in a real browserConnect 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.3 min read
GuidesWebLet Codex check its own work in a real browserAdd 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.2 min read
GuidesWebTest from Gemini CLI, the Claude desktop app and claude.aiInstall 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.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
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
GuidesWebRun plain-language browser tests in GitLab CIInclude 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.2 min read
GuidesWebRun browser tests from any CI with one fileCircleCI, Bitbucket, Jenkins, Buildkite or Azure Pipelines: one dependency-free script runs your saved tests, writes JUnit and exits non-zero on a failure.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
GuidesWebSend test failures to Slack, with the proof attachedConnect 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.2 min read
GuidesWebSend test results to Linear or Jira with webhooksTestsy 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.2 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
GuidesWebWhat a browser test suite costs when you pay per runNo 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.2 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
GuidesWebShare a live test run in a pull request, no account neededEvery 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.2 min read
GuidesiPhone and iPadAndroidTest an Expo app in CI without rebuilding it every timeNative 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.2 min read
GuidesAndroidBuild an Android APK that runs on cloud test devicesWhy 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.2 min read
GuidesiPhone and iPadBuild an iOS app for cloud testing: a zipped Simulator .appTestsy 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.2 min read
GuidesiPhone and iPadAndroidLet your coding agent test the mobile app it just builtClaude 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.2 min read
GuidesiPhone and iPadAndroidImport app builds from EAS, Bitrise or S3 by linkIf 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.1 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
GuidesWebCheck the record was saved, not just the success messageA 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.2 min read
GuidesWebMake Claude Code test what it just builtYour 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.4 min read
GuidesWebA daily check on every client site's key flowClients 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.4 min read
GuidesWebLet Cursor check its own work in a real browserConnect 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.3 min read
GuidesWebLet Codex check its own work in a real browserAdd 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.2 min read
GuidesWebTest from Gemini CLI, the Claude desktop app and claude.aiInstall 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.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
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
GuidesWebRun plain-language browser tests in GitLab CIInclude 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.2 min read
GuidesWebRun browser tests from any CI with one fileCircleCI, Bitbucket, Jenkins, Buildkite or Azure Pipelines: one dependency-free script runs your saved tests, writes JUnit and exits non-zero on a failure.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
GuidesWebSend test failures to Slack, with the proof attachedConnect 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.2 min read
GuidesWebSend test results to Linear or Jira with webhooksTestsy 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.2 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
GuidesWebWhat a browser test suite costs when you pay per runNo 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.2 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
GuidesWebShare a live test run in a pull request, no account neededEvery 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.2 min read
GuidesiPhone and iPadAndroidTest an Expo app in CI without rebuilding it every timeNative 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.2 min read
GuidesAndroidBuild an Android APK that runs on cloud test devicesWhy 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.2 min read
GuidesiPhone and iPadBuild an iOS app for cloud testing: a zipped Simulator .appTestsy 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.2 min read
GuidesiPhone and iPadAndroidLet your coding agent test the mobile app it just builtClaude 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.2 min read
GuidesiPhone and iPadAndroidImport app builds from EAS, Bitrise or S3 by linkIf 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.1 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
GuidesWebCheck the record was saved, not just the success messageA 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.2 min read
GuidesWebMake Claude Code test what it just builtYour 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.4 min read
GuidesWebA daily check on every client site's key flowClients 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.4 min read