> For the complete documentation index, see [llms.txt](https://docs.qapilot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qapilot.io/ai-and-core-concepts/how-qapilot-works.md).

# How QApilot Works

## How QApilot Works

QApilot helps teams create, run, and maintain mobile tests from one platform. It supports local and cloud execution for Android and iOS apps.

### The workflow

1. **Prepare a project and device**

   Create a [project](/ai-and-core-concepts/projects.md). Connect a [local device](/getting-started/set-up-qapilot/local-recording-and-execution.md) or configure [cloud execution](/getting-started/set-up-qapilot/cloud-device-recording-and-execution.md).
2. **Create coverage**

   Record interactions, use the Android crawler, or author with [CoWork](/ai-and-core-concepts/cowork-human-in-the-loop-mobile-test-authoring.md). QApilot stores the resulting interactions as test steps in reusable test cases.
3. **Organize and run tests**

   Group cases into [test suites](/test-creation/test-suite.md). Add test data or rules when needed. Then configure and launch a [test plan](/execution-and-reliability/run-mobile-test-plans.md).
4. **Review results and improve tests**

   Reports include execution details, screenshots, videos, logs, and rerun evidence. [AI auto-healing](/execution-and-reliability/ai-auto-healing-for-mobile-tests.md) can identify changed elements during a run.

### Choose the right creation mode

| Mode     | Use it when                                         | Current scope                        |
| -------- | --------------------------------------------------- | ------------------------------------ |
| Recorder | You need precise, repeatable interactions           | Android and iOS execution workflows  |
| Crawler  | You need autonomous Android app exploration         | Android apps; local or cloud devices |
| CoWork   | You have written cases and want AI-guided authoring | Android on LambdaTest                |

### How QApilot represents an app

The crawler explores screens and user paths. It records discovered interactions as structured test steps. QApilot describes this output as a knowledge graph of app flows and screens.

That structure supports later review, reuse, execution, and regression coverage. It does not replace product-specific test design. Add explicit cases for required business outcomes.

For the AI workflows that use this application understanding, see [AI-Native and Agentic Mobile Testing](/ai-and-core-concepts/ai-native-and-agentic-mobile-testing.md). Use [CoWork](/ai-and-core-concepts/cowork-human-in-the-loop-mobile-test-authoring.md) for reviewed, human-in-the-loop authoring.

### When to use QApilot

Use QApilot when you need to:

* Build repeatable mobile coverage from real interactions.
* Run tests on local devices or supported cloud device providers.
* Investigate failures with execution artifacts and step-level evidence.

### Related documentation

* [QApilot Getting Started](/getting-started/qapilot-getting-started.md)
* [Autonomous Test Generation](/ai-and-core-concepts/autonomous-android-test-generation.md)
* [CoWork: Human-in-the-Loop Mobile Test Authoring](/ai-and-core-concepts/cowork-human-in-the-loop-mobile-test-authoring.md)
* [Create Test Steps with the Test Recorder](/test-creation/record-mobile-test-steps/create-test-steps-with-the-test-recorder.md)
* [Reports](/reports-security-and-release-readiness/mobile-test-execution-reports.md)