testerarmy-cli

Create and run dashboard-managed QA tests with the TesterArmy CLI.

39.7k|4.4k|Updated Aug 26, 2021
One-click install
npx skills add https://github.com/novuhq/novu --skill testerarmy-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testerarmy-cli
Source: https://github.com/novuhq/novu/tree/main/.agents/skills/testerarmy-cli
Command: npx skills add https://github.com/novuhq/novu --skill testerarmy-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual QA testing and ad hoc browser checks produce no durable, repeatable coverage. This Skill turns acceptance criteria into persistent dashboard-managed tests, organized groups, and CI-visible runs using the TesterArmy CLI (ta).

Core Features & Use Cases

  • Dashboard Test Management: Create, inspect, and update saved tests with structured steps (act, assert, login, screenshot) scoped to projects and groups.
  • Local and Remote Runs: Execute saved tests locally for debugging or queue them in TesterArmy cloud with --remote --wait, including CI runs via ta ci.
  • Project Context & Credentials: Store site structure memories and login/inbox credentials so tests authenticate without embedding secrets in step titles.
  • Use Case: After shipping a new checkout flow, create a "Checkout smoke" test in the Smoke group, run it remotely against staging, and report the run ID and pass/fail result in your PR.

Quick Start

Ask the agent to check TesterArmy auth with ta status --json, then create a login flow test in your project and validate it with a remote run.

Frequently Asked Questions about testerarmy-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a QA test with the TesterArmy CLI?

Pipe a JSON payload with a title and steps array into `ta tests create --project <projectId> --json`. Steps use types like `act` for user actions, `assert` for expected outcomes, and `login` with a credentialId for authentication.

How do I run TesterArmy tests in CI?

Use `ta ci --group <groupId> --project <projectId> --target-url <url> --json` to execute a saved group against a target environment. This produces CI-visible results tied to your dashboard tests.

What is the difference between local and remote TesterArmy runs?

Without flags, `ta tests run` fetches the saved test and executes it in a local browser. Adding `--remote` queues the test in TesterArmy cloud, and `--wait` blocks until results are available; local-only flags like `--headed` are ignored remotely.

Does TesterArmy support mobile app testing?

Yes, you can upload an iOS Simulator build with `ta upload-app` and reference it in CI runs via `--app-id`. Supported formats include `.app`, `.zip`, and `.tar.gz`; `.ipa` and Android artifacts are not supported yet.

How do I handle login credentials in TesterArmy tests?

Create credentials with `ta projects credentials-create` and reference them in steps using `type: "login"` with a `credentialId`, or use `temporaryEmail` for inbox flows. Never put passwords directly in step titles or final messages.

When should I use ta run instead of saved dashboard tests?

Use `ta run "<prompt>"` only for quick ad hoc exploration of a flow. For durable, repeatable coverage, create tests with `ta tests create` and run them through groups so results persist in the dashboard.