Choose a QA.army Interface | QA.army

Use the app for visual work, the CLI for terminal workflows, and the public API when you need to integrate supported operations. They use the same model:

Workspace -> Project -> Test Group -> Test -> Run

Interface	Use it for	Start here
App	Set up a Project, edit Tests, start Web Runs, and review evidence	Quick Start
CLI	Save Tests and operate supported Web Runs from a terminal or coding agent	Install and use the CLI
API	Integrate documented operations with an authorized credential	API Access
MCP	Structured agent tools when a supported connection is available	MCP availability
Chatbot	Conversational product access; currently unavailable	Chatbot availability

The public website explains the product. It does not operate Workspace data.

Choose access for the task

An agent’s setup access covers discovery, saving Tests, and supported Run operations. It does not grant all the permissions of a signed-in user. Updating Tests, organizing Test Groups, or cancelling Runs requires a supported user session or profile API key. Test Account access requires a signed-in user session.

Use the app when a task needs interactive authorization or evidence review. Use the coding-agent guide for direct Test authoring, safe retries, and reporting actual results. Changing interfaces does not expand Workspace access or change a Run’s verdict.

Check target availability

Direct Web testing is available. Native Android, iOS, and Desktop execution are not generally available. A mobile-sized browser viewport is a Web Test, not proof of native app coverage. Local-only targets need a supported connection; see Local Development.