Agent skill · software engineering · sickn33
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
Why this skill is useful
Adds specific ADB commands and XML parsing patterns for automating Android UI journey tests that the AI wouldn't reliably generate on its own.
What it needs
Requires adb installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Android UI Journey Testing Overview This skill outlines the standard workflow for running XML-specified User Journey tests on Android applications. A "journey" is a sequenced set of user actions and state assertions designed to verify end-to-end functionality. The journey XML acts as the source of truth for the app's behavior. The executor proceeds sequentially, performing UI interactions, checking state assertions, and writing a standardized JSON outcome report. When to Use Use when evaluating an Android application's UI behavior against an XML test specification. Use when automating multi-step user flows (e.g., login, checkout, navigation) and verifying expectations. Use when running verification tests and generating standardized JSON test reports. Use when debugging application flows on physical devices or emulators using ADB commands. How It Works Step 1: Parse the Journey Specification Read and parse the XML test suite structure. The root node <journey> defines the test case name, and the <actions> block contains the sequence of test steps. Step 2: Sequential Step Evaluation Process each <action> element in the exact order specified. Test steps are classified into two groups: A. Interactive Actions (Taps, Swipes, Text Input) Perform the physical UI interaction using ADB. Tapping: Tap the center of the target element's bounds: Swiping/Scrolling: Swipe from coordinate to coordinate with a duration: Text Typing: Type text into the active input field: If the element is missing or the action cannot be performed, the action and the journey fail. B. State Assertions (Expectation Verification) Steps beginning with "verify", "check", or "ensure" represent state assertions. Inspect the current screen (using screenshots or uiautomator dump) without interacting or scrolling. Confirm all sub-assertions are met. For example, "Verify that the app is on the Home screen and the logo is visible" fails if the home screen is not displayed or the logo is missing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/android-ui-journey-testing