--- name: "android-emulator-qa" description: "Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture." --- # Android Emulator QA Validate Android app flows in an emulator using adb for launch, input, UI-tree inspection, screenshots, and logs. ## When to use - QA a feature flow in an Android emulator. - Reproduce UI bugs by driving navigation with adb input events. - Capture screenshots and logcat output while testing. ## Quick start 1) List emulators and pick a serial: - `adb devices` 2) Build and install the target variant: - `./gradlew ::install --console=plain --quiet` - If unsure about task names: `./gradlew tasks --all | rg install` 3) Launch the app: - Resolve activity: `adb -s shell cmd package resolve-activity --brief ` - Start app: `adb -s shell am start -n /` 4) Capture a screenshot for visual verification: - `adb -s exec-out screencap -p > /tmp/emu.png` ## adb control commands - Tap (use UI tree-derived coordinates): - `adb -s shell input tap ` - Swipe: - `adb -s shell input swipe ` - Avoid edges (start ~150-200 px from left/right) to reduce accidental back gestures. - Text: - `adb -s shell input text "hello"` - Back: - `adb -s shell input keyevent 4` - UI tree dump: - `adb -s exec-out uiautomator dump /dev/tty` ## Coordinate picking (UI tree only) Always compute tap coordinates from the UI tree, not screenshots. 1) Dump the UI tree to a step-specific file: - `adb -s exec-out uiautomator dump /dev/tty > /tmp/ui-settings.xml` 2) Find the target node and derive center coordinates (`x y`) from bounds: - Bounds format: `bounds="[x1,y1][x2,y2]"` - Helper script: - `python3 /scripts/ui_pick.py /tmp/ui-settings.xml "Settings"` 3) If the node is missing and there are `scrollable` elements: - swipe, re-dump, and re-search at least once before concluding the target is missing. 4) Tap the center: - `adb -s shell input tap ` ## UI tree skeleton (helper) Use this helper to create a compact, readable overview before inspecting full XML. 1) Dump full UI tree: - `adb -s exec-out uiautomator dump /dev/tty > /tmp/ui-full.xml` 2) Generate summary: - `python3 /scripts/ui_tree_summarize.py /tmp/ui-full.xml /tmp/ui-summary.txt` 3) Review `/tmp/ui-summary.txt` to choose likely targets, then compute exact bounds from full XML. ## Logs (logcat) 1) Clear logs: - `adb -s logcat -c` 2) Stream app process logs: - Resolve pid: `adb -s shell pidof -s ` - Stream: `adb -s logcat --pid ` 3) Crash buffer only: - `adb -s logcat -b crash` 4) Save logs: - `adb -s logcat -d > /tmp/logcat.txt` ## Package shortcuts - List installed packages: - `adb -s shell pm list packages` - Filter to your namespace: - `adb -s shell pm list packages | rg ` - Confirm the activity resolves before launching: - `adb -s shell cmd package resolve-activity --brief `

android-emulator-qa

Install this skill

Comments