How QApilot Works
Learn how QApilot turns mobile app flows into reusable tests through AI exploration, recording, execution, and evidence-rich reporting.
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
Prepare a project and device
Create a project. Connect a local device or configure cloud execution.
Create coverage
Record interactions, use the Android crawler, or author with CoWork. QApilot stores the resulting interactions as test steps in reusable test cases.
Organize and run tests
Group cases into test suites. Add test data or rules when needed. Then configure and launch a test plan.
Review results and improve tests
Reports include execution details, screenshots, videos, logs, and rerun evidence. AI auto-healing can identify changed elements during a run.
Choose the right creation mode
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. Use CoWork 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
Last updated