# QA.army | Documentation

## Instructions for AI Agents

- For clean Markdown of any page, append `.md` to the page URL
- For section-specific indexes, append `/llms.txt` to any section URL
- For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.qa.army/_mcp/server

## Docs

- [Welcome to QA.army](https://docs.qa.army/welcome.md): Understand QA.army's always-on QA mission, product model, platforms, and current availability.
- [Introduction](https://docs.qa.army/get-started/introduction.md): Learn what QA.army does and how it helps teams maintain reliable product journeys.
- [How QA.army Works](https://docs.qa.army/get-started/how-qa-army-works.md): See how QA.army turns important product journeys into readable tests and clear results.
- [Core Concepts](https://docs.qa.army/get-started/core-concepts.md): Learn how QA.army's workspaces, projects, test groups, tests, runs, environments, triggers, and evidence fit together.
- [Start with QA.army](https://docs.qa.army/get-started/quick-start.md): Create a Workspace, save one critical Web Test, and use the first of 10 free Runs.
- [Plans and Usage](https://docs.qa.army/account/plans-and-usage.md): Understand QA.army's 10 initial free Runs and what counts as a Run.
- [Projects and Environments](https://docs.qa.army/projects-and-environments.md): Organize each product surface and choose where its tests should run.
- [Test Accounts and Files](https://docs.qa.army/test-accounts-and-files.md): Prepare reusable accounts and upload fixtures without exposing sensitive information.
- [Product Memory](https://docs.qa.army/docs/set-up-your-project/product-memory.md): Teach QA.army your product and review what it learns.
- [Authenticated Journeys](https://docs.qa.army/authenticated-journeys.md): Prepare email, one-time-code, phone, and sign-in journeys without placing credentials in test steps.
- [Protected Applications](https://docs.qa.army/protected-applications.md): Plan coverage for applications behind sign-in, allowlists, and other access controls.
- [Write Reliable Test Steps](https://docs.qa.army/write-reliable-test-steps.md): Express intent clearly and make outcomes observable.
- [Organize Tests into Groups](https://docs.qa.army/organize-tests-into-groups.md): Group durable journeys by product purpose and ownership.
- [Create and Start Runs](https://docs.qa.army/create-and-start-runs.md): Prepare, start, watch, and cancel a saved Test run.
- [Run Configuration](https://docs.qa.army/run-configuration.md): Plan environments, ordering, viewport, location, and shared setup for a test run.
- [Results and Evidence](https://docs.qa.army/results-and-evidence.md): Understand test results and the evidence available for each run.
- [Accessibility Checks](https://docs.qa.army/accessibility-checks.md): Plan optional accessibility findings alongside functional Web coverage.
- [Recordings](https://docs.qa.army/recordings.md): Understand how recordings support replay, reproduction, and bug reporting.
- [Automation Overview](https://docs.qa.army/automation.md): Understand explicit Runs, assisted PR testing, and upcoming automated triggers.
- [GitHub Pull Request Testing](https://docs.qa.army/github-pull-request-testing.md): Verify changed behavior on the matching Vercel preview during the assisted pilot.
- [Production Monitoring](https://docs.qa.army/production-monitoring.md): Understand planned scheduled coverage for critical journeys.
- [CI and Deployments](https://docs.qa.army/ci-and-deployments.md): Use a saved Web Test in a script, interpret its exit code, and distinguish a Run from deployment verification.
- [Preview Environments](https://docs.qa.army/preview-environments.md): Prepare change-specific Web targets for pull-request and deployment testing.
- [Notifications and Issue Tracking](https://docs.qa.army/notifications-and-issues.md): Plan who should be notified and what a useful QA issue should contain.
- [Web Testing](https://docs.qa.army/platforms/web.md): Prepare critical browser journeys and the evidence needed to understand them.
- [Android and iOS Testing](https://docs.qa.army/platforms/mobile.md): Upload and verify immutable Android and iOS builds in a Mobile Project.
- [Desktop Testing](https://docs.qa.army/platforms/desktop.md): Prepare critical desktop journeys without implying unattended execution is live.
- [Choose a QA.army Interface](https://docs.qa.army/web-cli-and-mcp.md): Choose the app, CLI, or public API for setup, saved Web Tests, Runs, and evidence review.
- [QA.army CLI](https://docs.qa.army/interfaces/cli.md): Install the CLI, authorize access, save a Web Test, run it, and inspect the result from your terminal.
- [QA.army MCP](https://docs.qa.army/interfaces/mcp.md): Connect a local MCP client, maintain saved Tests, and inspect Runs with the same account authorization as the CLI.
- [QA.army SaaS App](https://docs.qa.army/interfaces/saas-app.md): Use QA.army's visual interface according to your role, decision, and product target.
- [QA.army Chatbot](https://docs.qa.army/interfaces/chatbot.md): Understand how conversational access fits QA.army and which boundaries keep product state trustworthy.
- [Use QA.army with Coding Agents](https://docs.qa.army/interfaces/coding-agents.md): Author saved Tests from application requirements, run them, and inspect the evidence through the public API.
- [Test Local Development](https://docs.qa.army/interfaces/local-development.md): Understand the planned boundary for testing a developer's local product build.
- [API Access](https://docs.qa.army/interfaces/api-access.md): Find the public authentication and API contracts, choose authorized operations, and handle retries safely.
- [Security and Privacy](https://docs.qa.army/security-and-isolation.md): Understand workspace access, test credentials, and evidence privacy.
- [Run Statuses and Errors](https://docs.qa.army/troubleshooting/runs.md): Interpret a run outcome and choose the right next action.
- [Account and Access Problems](https://docs.qa.army/troubleshooting/accounts.md): Prepare to resolve sign-in, membership, and test-account problems safely.
- [Migrate Existing Web Tests](https://docs.qa.army/migrate/web-tests.md): Prepare readable QA.army coverage from an existing browser test suite.
- [Migrate Existing Mobile Tests](https://docs.qa.army/migrate/mobile-tests.md): Prepare Android and iOS journeys from an existing mobile test suite.
- [Glossary](https://docs.qa.army/reference/glossary.md): Definitions for the customer-facing objects and results used throughout QA.army.
- [Frequently Asked Questions](https://docs.qa.army/reference/faq.md): Customer answers about setup, availability, results, evidence, access, and interfaces.
- [AI-Readable Documentation](https://docs.qa.army/reference/ai-readable-docs.md): Give coding agents a reliable path to QA.army's current public documentation.