Mobile Testing Skill

Automated Android app testing on an emulator using the Android DevTools CLI. Drives an AVD over adb: connect, act on the UI, read the UI/accessibility tree, capture screenshots/recordings/logcat, and verify.

When to Use

This skill activates when:

• User asks to test an Android app or mobile UI flow
• User wants to automate taps/swipes/typing on an emulator
• User needs to verify Android app behavior (navigation, forms, login/checkout)
• User wants to capture logcat or app performance during a flow
• User wants to inspect, mock, or intercept the app's HTTP(S) requests, or correlate them to a backend by trace id
• User mentions an AVD, emulator, deep link, or adb

Emulator only — no physical devices, no iOS. For web pages use browser-testing; for server APIs use backend-testing.

Verification model

There is no assert tool. Trigger an action, then read raw observations and judge for yourself. Default to the UI tree (a11y take-ui-snapshot) — it is structured, gives stable refs, and is the cheap way to confirm state. Screenshot only for visual-only state or once after a screen change, not after every step.