> 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/autonomous-android-test-generation.md).

# Autonomous Android Test Generation

## Autonomous Android Test Generation

QApilot's crawler autonomously explores Android applications and records discovered interactions as reusable test steps. Use it to map app paths, find potential issues, and establish initial regression coverage.

A crawler is an intelligent test exploration engine. It navigates through the app to discover user flows, UI components, and potential issues with minimal manual intervention.

### How it Works in the QApilot Context?

* **Supported Platforms**
  * Currently, Crawlers in QApilot are designed for **mobile applications on Android OS**.
  * iOS crawler support is **under implementation** and will be available in upcoming releases.
* **Execution Modes**
  * **Crawl Local** → Run the crawler on a locally connected Android device/emulator.
  * **Crawl Remote** → Run the crawler on a **cloud-based Android device farm** (BrowserStack, Sauce Labs, LambdaTest).
* **Recording**
  * In both local & remote modes, the crawler **records the interactions** into structured test steps.
  * In both Local and Remote modes, the crawler automatically records interactions as structured test steps, which are then stored directly into Test Cases for reuse and execution.
* **Crawl Reports**
  * All crawler runs (local or remote) are stored in **Crawl Reports**, where you can:
    * Review steps.
    * Compare across builds.
    * Track coverage.
    * Promote recorded flows into regression suites.

For a broader explanation of this workflow, see [AI-Native and Agentic Mobile Testing](/ai-and-core-concepts/ai-native-and-agentic-mobile-testing.md).