Verify Android UI with automated ADB testing

Android UI Verification Skill provides a systematic approach to testing React Native applications on an Android emulator using ADB commands. It allows autonomous interaction with the app, state verification and visual regression checking. Its description calls it automated end-to-end UI testing and verification on an Android Emulator using ADB.

The workflow has four parts.

Device calibration: before interacting, always verify the screen resolution so tap coordinates are accurate. The skill notes that layouts are often scaled and that you should use the physical size returned by the size command as the base for coordinate calculations.

UI inspection, or state discovery: use a uiautomator dump to find the exact bounds of UI elements such as buttons and inputs. The dump is pulled to an artifacts folder as view.xml. You then search it for text, content-desc or resource-id, and the bounds attribute in the form [x1,y1][x2,y2] defines the clickable area.

Interaction commands: tap (use the center of the element bounds), swipe (used for scrolling, with start and end coordinates and a duration in milliseconds), text input (with limited support for special characters), and key events (for example code 66 for Enter).

Verification and reporting: visual verification captures a screenshot after an interaction to confirm UI changes, and analytical verification monitors the JS console logs to detect errors or successes. Generated files should always be stored in the artifacts folder to satisfy project organization rules.

adb shell wm size

Use it to verify UI changes in React Native or native Android apps, to debug layout issues or interaction bugs autonomously, to confirm feature functionality when manual testing is too slow, and to capture automated screenshots for PR documentation.

Do not use it without the prerequisites: an Android emulator must be running, adb must be installed and on your PATH, and the application must be in debug mode so logcat is accessible. The Limitations section also says to use the skill only when the task clearly matches this scope, not to treat its output as a substitute for environment-specific validation, testing or expert review, and to stop and ask if required inputs, permissions, safety boundaries or success criteria are missing.

Inputs are a running emulator and a debug build of the app. Outputs are UI element bounds read from the dump, screenshots saved as test result images in the artifacts folder, and the last lines of the ReactNativeJS log filtered from logcat output, which show errors or success messages.

The best practices keep runs reliable:

• Wait for animations by adding a short sleep of 1 to 2 seconds between an interaction and its verification.
• Center taps by calculating the arithmetic mean of the two bounds corners, which gives the most reliable tap target.
• Use distinct log markers in the code, such as a checkmark message for a successful action, so grep verification is easy.
• Fail fast: if a uiautomator dump fails or does not find the expected text, stop and troubleshoot rather than blind-tapping.

The skill relies on adb, uiautomator and logcat, and on the React Native JavaScript console log tag. It works with the Android Emulator and with PR documentation that needs screenshots.

React Native and Android developers, QA engineers and agents that need to verify UI behavior on an emulator without manual tapping. It is marked safe in its metadata and comes from a community source added in February 2026.