For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Discord
DocsAPI Reference
DocsAPI Reference
  • Get Started
    • Welcome
    • Introduction
    • Quick Start
  • Run
    • Run Videos
    • Run Mode
    • Viewport Size
    • Preparation Test
    • Pull Request Testing
    • Production Monitoring
    • Group Webhooks
    • Run Troubleshooting
  • Auth
    • Test Credentials
    • API Keys
    • Agent Mail Inboxes
    • HTTP Basic Auth
    • Auth Troubleshooting
  • Mobile
    • Overview
    • App Uploads
    • Expo EAS
    • GitHub Actions
  • Integrations
    • Vercel
    • Coolify
    • Custom Infrastructure
    • Slack
    • Discord
    • Email
  • Guides
    • Testing Staging Environment
  • CLI
    • Getting Started
    • Local Development
    • Agentic Usage
  • AI
    • LLMs
LogoLogo
Discord
On this page
  • 1. Create an account
  • 2. Install and authenticate the CLI
  • 3. Prompt your agent
  • 1. Create an account
  • 2. Create a project
  • 3. Create a test
  • Next steps
Get Started

Quick Start

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Introduction

Next

Run Videos

Built with
With Agent
Manual

Let your coding agent set up TesterArmy for you using the CLI.

1. Create an account

Sign up at tester.army.

2. Install and authenticate the CLI

$npm install -g testerarmy
$testerarmy auth

Generate a key in the API Keys dashboard and paste it when prompted. The CLI stores it locally for future commands.

3. Prompt your agent

Use the TesterArmy CLI (`testerarmy`) to set up QA for this project.
Create a project, generate a test, run it, and report the run ID and
results. Use `testerarmy --help` and prefer JSON output.

The agent will create the project, draft tests, and execute them - without you leaving your editor. See Agentic Usage for the full workflow.

Congrats! You successfully created and executed your very first test!

Testing is all about consistency, you should set up Production Monitoring or PR Testing to guarantee everything keeps working.

Next steps

PR Testing

Automatically test every pull request on deploy.

Production Monitoring

Monitor your production with recurring test runs.