Every hour, daily, weekly or cron
Pick a preset or write a cron expression, and the whole group runs at that time.
[02] Runs on a schedule
Production checks
that run on a schedule
Pick a test group, choose hourly, daily, weekly or cron, and agents click through production at that time.
One trigger per test group
Each group carries its own Production Monitoring schedule and an optional webhook, so checks run without anyone pressing Run All.
Production or custom
Point the schedule at Production, at Staging, or at any custom URL you choose for the run.
Real test accounts
Agents sign in with the Test Account you assign, so checks behind login run like a real user.
Fresh results every run
Every scheduled run lands in Results with its status, duration and environment, ready to open.
Watch an agent test your app this week
Start a production schedule yourself, or book a walkthrough and set it up with us.
[03] When something breaks +
When something breaks
A failed run posts a summary and a run link to Slack, Discord or email, and the failing step waits in Results with its screenshots and recording.
Slack alert
A failed scheduled run posts the test name, the failing step and a link to the run.
The failing step
Open the run to see which step failed, with the screenshots and recording from that moment.
Failed run in Results
Failed runs sit in the same Results table as passed ones, filtered in one click.
Issue summary
Each run ends with a short summary of what failed, in Results and wherever the alert lands.
Alerts where you work
The summary and run link go to Slack, Discord or email the moment a check fails.
[04] Explore the platform +
Run at every step of shipping
The same tests run on every pull request, from your CI job, on a schedule against Production, or by hand. Every run lands in one Results table.
Web apps in a real browserWeb testingiOS and Android from a buildMobile app testingReact Native on both platformsReact NativeExpo builds in your EAS workflowExpoWordPress sites before every updateWordPressCheckout tested like a shopperEcommerceOne CI job after deployCI/CD testingCoding agents over one MCP endpointCoding agents
[04] Proof
Teams that stopped checking
production by hand
I used to manually check production after every deploy, just to be safe. With TesterArmy, I leave the office and wait for the Slack message.
Benedict Chan
Co-Founder, Lightsprint
FAQ
Frequently asked questions
Can we test against staging too, or only production?
Both. Point your tests at staging, preview deployments or production. A group's schedule can target Production, Staging or a custom URL.
Can it test journeys behind authentication and SSO?
Yes. Assign a Test Account to the test so agents can sign in. Email and password, OAuth, magic links and verification emails are supported; your application's authentication requirements determine the account setup.
Where do you store our test credentials?
Test Account credentials are encrypted at rest and scoped to your project. The dashboard shows masked values, and you can update or remove an account from Test Accounts.
How often can scheduled checks run?
Choose hourly, daily or weekly presets, or enter a custom cron expression. The schedule belongs to a test group, so its saved tests run together at the time you set.
What does an alert look like and where does it go?
A scheduled run's notification summarizes the outcome and links to the run. Connect Slack or Discord, or configure email notifications. Open the run for the step-by-step results, screenshots and recording.
How long does it take to get the first journey running?
Add your production URL, describe a critical flow in plain English and run it. Once the test is saved in a group, choose the group's schedule. No SDK or test scripts are required.
How is this different from Datadog Synthetics or Checkly?
TesterArmy agents execute journeys described in plain English and adapt to the interface as they run. You can check signup, checkout and authenticated dashboards without maintaining a scripted sequence of selectors, and inspect the evidence from each run.
What happens when a scheduled run fails?
The failed run appears in Results alongside the checks that passed. Open it to inspect the failing step, screenshots and recording, or follow the run link in your configured notification channel.
