Skip to main content
TesterArmy executes tests in the cloud. To validate development changes, deploy a preview or expose your dev server through a tunnel and use its reachable URL. A cloud browser cannot reach your machine’s localhost address directly. Local CLI execution and its hosted inference proxy have been removed. Update older CLI installations and use cloud runs, which follow your team’s existing plan limits and usage.

​
Save a development environment

Start your app and obtain a preview or tunnel URL, then save it on the project:
Use the returned environment name or slug for subsequent runs. If a temporary tunnel URL changes, create an environment with the new URL.

​
Run saved tests

Single-test runs select their target through --env or --project-environment-id. Use --wait-timeout <ms> to adjust how long the CLI waits for results.

​
Inspect results

Runs appear in the dashboard with their recordings and step results. From the terminal, inspect a run using the ID returned by the run command:
Console and network telemetry (app logs for mobile runs) becomes available after the run finishes. Save the JSON response with shell redirection when you need a local artifact:

​
CI usage

Run a group against the preview URL produced by your deployment step:
ta ci waits for results and exits unsuccessfully for failed, blocked, cancelled, or timed-out runs. See Direct CLI usage and Custom infrastructure for more CI options.