Native App Automation Appium (Overview)

Native App Automation uses Appium with the lambda-accessibility-scan hook to generate accessibility results during Android or iOS test runs on the TestMu AI grid.

When to use this

Use this page when your team already runs Appium for functional tests and wants accessibility checks in the same execution path with deterministic checkpoints.

Prerequisites

Appium client and test project targeting TestMu AI real devices or emulators per your subscription
LT_USERNAME / LT_ACCESS_KEY available to the process
Accessibility enabled on the mobile session (see framework guides below for capability examples)

Onboarding: first automated mobile accessibility run

Reuse a green Appium suite without accessibility first—confirm install, locators, and hub connectivity.
Add accessibility capability on the session (exact key names align with your Appium server version; mirror the examples in Appium TestNG or Appium WebdriverIO).
After each stable screen (post-navigation waits), call:

driver.executeScript("lambda-accessibility-scan");

Run a single test method to validate a report appears under Accessibility for that build.
Open Navigating the Dashboard and locate the session’s accessibility report.
Expand coverage to full suites only after reports look stable.

Typical workflow (summary)

Upload the app and configure the Appium session.
Enable Accessibility in the session capabilities.
Trigger lambda-accessibility-scan at important checkpoints.
Review the report in the dashboard.

Product boundary

This page is for direct Appium-based automation. If you are authoring the flow in KaneAI, use Mobile App Accessibility Testing. If you want manual screen-by-screen testing, use Accessibility App Scanner (Overview).