CLI

Agentic Usage

View as Markdown

Give your coding agent access to the TesterArmy CLI when you want it to set up and run QA without leaving your development loop.

The CLI is designed to be self-discoverable. Agents should start with ta agent init and ta docs instead of scraping long help output. ta docs prints task-oriented command routing, and --json returns structured output for automation.

What agents can do

With an API key, an agent can:

  • create and list projects
  • create and delete static project environments
  • save project memories as durable testing context
  • create dashboard tests
  • run tests locally or remotely
  • wait for remote runs and inspect run history
  • upload iOS Simulator apps and Android artifacts for mobile tests

Setup

Install and authenticate once:

$npm install -g testerarmy
$ta agent init
$ta auth
$ta status --json

For non-interactive sessions, set:

$export TESTERARMY_API_KEY="YOUR_KEY"

Prompt your agent

Use TesterArmy CLI (`ta`) for QA. Start with `ta agent init`, then discover
workflows with `ta docs --json` or `ta docs <topic>`. Use `--json` for automation;
on failure, follow `error.hint`. Report commands, run IDs, results, and artifacts.

Useful entrypoints

$ta agent init
$ta docs
$ta docs --json
$ta docs agent
$ta docs projects
$ta docs memories
$ta docs tests
$ta docs runs
$ta docs ci

Safety

  • use scoped API keys when possible
  • prefer --json for agent-readable output
  • use JSON error envelopes to decide the next action instead of parsing text
  • avoid putting secrets in shell history
  • ask before deleting projects, environments, memories, or tests