Local Development
Use the CLI to validate changes against your local dev server before pushing.
ta tests run queues remote dashboard runs by default. Local execution is the
exception for dev-server loops: pass --local to run dashboard tests in a
local browser on your machine.
Set your target URL
Set the target once for the session:
Or pass it per-run:
Run tests
Start your dev server, then run dashboard-defined tests locally:
Add project memory
Use memories to give the agent durable project context before it runs tests:
Headed mode
Watch the AI agent work in a visible browser:
Useful for debugging flaky tests or understanding agent behavior.
Debug mode
Save detailed logs and transcripts to .testerarmy/:
Check .testerarmy/<timestamp>/debug-run.json for the full stream/tool transcript.
Inspect artifacts
Every run writes to .testerarmy/<timestamp>/:
run-meta.json- run metadataresult.json- pass/fail resultsdebug-run.json- full transcript (with--debug)
List recent runs:
Typical workflow
CI usage
Prefer remote runs in CI so results land in the dashboard — see
ta ci or ta tests run --group <groupId> --project <id> --wait --json.
To execute on the CI machine’s own browsers instead, set TESTERARMY_API_KEY
and TESTERARMY_TARGET_URL and pass --local:
Exit code 1 on any test failure - your pipeline fails automatically.
