> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.qa.army/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.qa.army/_mcp/server.

# Projects and Environments

> Organize each product surface and choose where its tests should run.

## Project

A Project represents one independently testable Web, Android, iOS, or Desktop
product surface. Android and iOS use the Mobile Project type. A Project contains
Test Groups, Tests, environments, integrations, test accounts, files, and Run
history.

> **Warning**
>
> Authorized users can create Web and Mobile Projects. Direct Web execution and
> Mobile build registration are available. Desktop Project setup and native
> Android, iOS, and Desktop execution are not generally available.

## Environment

An Environment identifies the target for a Test. Common Web environments include Production, Staging, QA, and PR Preview.

Configure approved environments once, then choose the appropriate target when preparing a Run. Workspace membership controls who can view or change Project settings.

## Use one Project per surface

Use separate Projects when applications have different release cycles, credentials, environments, owners, or platform types. Keep related journeys in Test Groups within the same Project.