Agent skill · software engineering · sickn33
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
Why this skill is useful
Adds specific ADB commands and workflows for automated UI testing on Android that the AI wouldn't reliably generate on its own.
What it needs
Requires adb installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Android UI Verification Skill This skill provides a systematic approach to testing React Native applications on an Android emulator using ADB commands. It allows for autonomous interaction, state verification, and visual regression checking. When to Use Verifying UI changes in React Native or Native Android apps. Autonomous debugging of layout issues or interaction bugs. Ensuring feature functionality when manual testing is too slow. Capturing automated screenshots for PR documentation. 🛠 Prerequisites Android Emulator running. adb installed and in PATH. Application in debug mode for logcat access. 🚀 Workflow 1. Device Calibration Before interacting, always verify the screen resolution to ensure tap coordinates are accurate. Note: Layouts are often scaled. Use the physical size returned as the base for coordinate calculations. 2. UI Inspection (State Discovery) Use the uiautomator dump to find the exact bounds of UI elements (buttons, inputs). Search the view.xml for text, content-desc, or resource-id. The bounds attribute [x1,y1][x2,y2] defines the clickable area. 3. Interaction Commands Tap: adb shell input tap <x> <y> (Use the center of the element bounds). Swipe: adb shell input swipe <x1> <y1> <x2> <y2> <durationms> (Used for scrolling). Text Input: adb shell input text "<message>" (Note: Limited support for special characters). Key Events: adb shell input keyevent <codeid> (e.g., 66 for Enter). 4. Verification & Reporting Visual Verification Capture a screenshot after interaction to confirm UI changes. Analytical Verification Monitor the JS console logs in real-time to detect errors or log successes. Cleanup Always store generated files in the artifacts/ folder to satisfy project organization rules. 💡 Best Practices Wait for Animations: Always add a short sleep (e.g., 1-2s) between interaction and verification. Center Taps: Calculate the arithmetic mean of [x1,y1][x2,y2] for the most reliable tap target. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/android_ui_verification--442fc9