Login step
The agent signs in with a Test Account before the flow begins.
[02] Tests written in plain language
Tests written in
plain language
Each test is a list of steps a teammate could read, from logging in to checking what appears on screen.
Steps you can read
Login, Act, Assert and Screenshot steps, saved with their run history.
Act step
One plain sentence per action, from opening a page to filling a form and clicking through.
Assert step
The agent checks what a user would see on screen and marks the step passed or failed.
Screenshot step
A screenshot step captures the page at that moment and attaches it to the run report.
Start with the flows your users depend on
Create your first test in plain language and run it in a real browser.
[03] Real accounts, real browser +
Real accounts, real browser
Every run opens a real browser session, signs in with the Test Account you choose and works through the flow on Production, Staging or a PR Preview.
Every run in
a real browser
Results lists each run with its status, platform and environment; opening one shows the transcript beside the live browser.
Test Accounts
Save the accounts agents sign in with once and reuse them across tests and environments.
Environments
Point the same test at Production, Staging, a PR Preview or any custom URL.
Desktop viewport
Agents drive a real desktop browser, so layouts, menus and dialogs behave as they do for users.
Recording and screenshots
Each run keeps a recording and the screenshots the steps captured, ready to open from the report.
[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 ship web apps
with agents on the flows
Automatic auth with test accounts was the blocker that killed our earlier QA attempts, and now we monitor our logged-in dashboard continuously without thinking about it.
Witold de La Chapelle
Co-Founder and CTO, Standout
FAQ
Frequently asked questions
Does it work with our framework?
Yes. Agents interact with the rendered app in a real browser. Next.js, React, Vue, Svelte, Rails, Django and plain HTML work through the same browser interface.
Can we run against Vercel previews on every PR?
Yes. Connect the TesterArmy GitHub App and your Vercel project to run saved tests against preview deployments. Results and report links appear on the pull request.
Can it test flows behind auth?
Yes. Save a Test Account and use a Login step to sign in before the rest of the flow. Accounts can be reused across tests and assigned to the appropriate environment.
Can agents handle OTP codes during login?
Agents can read verification emails and use configured one-time-password credentials. Set up the Test Account and any required email or authenticator details for the login flow.
Can it test localhost or a private network?
Hosted agents need a reachable app URL. Expose your development server through a tunnel, or use a reachable staging or preview deployment, then select that URL as the test environment.
How is this different from Playwright or Cypress?
With TesterArmy, you describe steps in plain language and agents carry them out in the browser. The service manages execution and collects the recording, screenshots and report, without requiring you to maintain a script of selectors.
Which viewports and browsers do runs use?
Web tests use a real desktop browser. The run report includes the browser recording and screenshots so you can inspect the layout and interactions the agent saw.
Do failed runs include recordings and screenshots?
Yes. Open a run to inspect its steps, transcript and recording. Screenshots captured during the run and explicit Screenshot steps are available with the report.
