Glossary

Workspace

The home for one team’s Projects, members, access, usage, and billing.

Project

One independently testable Web, Android, iOS, or Desktop product surface. Android and iOS are represented by the Mobile Project type.

Environment

An approved target for a Test, such as Production, Staging, QA, or a pull-request preview.

Test Group

A collection of related customer journeys within one Project, such as Authentication, Checkout, or Billing.

Test

The saved definition of one journey, including its ordered steps, assertions, settings, and evidence requirements.

Step

One action or assertion within a Test. Good steps use plain language and name an observable outcome.

Run

One requested execution of one saved Test in one Environment.

Trigger

The reason a Run was requested, such as an explicit action in the app or CLI. Schedules and automatic product-change triggers have separate availability.

Evidence

Information that helps explain and reproduce a Run result. Depending on availability, it can include timestamps, assertions, screenshots, recordings, console messages, network activity, and reproduction steps.

Result

The final outcome of a Run:

• PASSED: every required assertion succeeded.
• FAILED: the journey ran and a product assertion failed.
• ERROR: QA.army could not determine a reliable product result.
• CANCELLED: the Run stopped before completion.

Core Test Group

Saved, durable coverage for journeys your team already knows are important.

Dynamic Test

Change-focused coverage for a specific pull request. Dynamic pull-request testing is an assisted pilot and is not generally available.

Interface

A presentation of the same QA.army product model. The SaaS app is visual, the CLI is terminal-oriented, MCP is agent-native, and the chatbot is conversational. See Choose an Interface for supported tasks and availability.

Setup access

The limited operations available to a registered agent after its human claim is complete: discover authorized Workspaces and Projects, manage Test Groups, create and update saved Tests, and create, start, inspect, or cancel Runs. Workspace Owners can also manage an existing connected deployment watch.

These capabilities still require current Workspace membership. They do not grant Test deletion, Test Account metadata or credentials, Live View, membership changes, billing, or integration consent. Provisional registration alone is not a completed claim.

Idempotency key

A value that identifies one intended API operation. Reusing the same key with the same payload lets a supported request recover from an uncertain response without deliberately asking for duplicate work. A new Run needs a new operation.

Terminal status

A completed Run outcome: PASSED, FAILED, ERROR, or CANCELLED. READY and an accepted start request are not terminal outcomes.

Target platform

The independently testable product surface owned by a Project: Web, Android, iOS, or Desktop. Product scope does not imply that execution is available.