Android Testing UI

When To Use

Use this skill when the request is about: android ui test, compose ui test screen, espresso validation android.
Primary outcome: Validate Android UI behavior with Compose UI tests, Espresso-style checks, screenshot assertions, and accessibility verification.
Reach for this skill when the missing work is assertions, instrumentation, screenshot capture, or accessibility verification, not product-state design.
Handoff skills when the scope expands:
android-compose-accessibility
android-ui-states-validation

Scope the risk surface: behavior, visual regressions, accessibility semantics, or cross-device interaction.
Pick the narrowest verification strategy that still catches the likely regressions: instrumentation for behavior, Roborazzi for visuals, or both for high-risk flows.
Instrument the workflow so failures are actionable rather than just red.
Run the relevant checks on the showcase apps and packaging outputs.
Capture any residual risk with explicit follow-up work and owner skills, including handing off to android-ui-states-validation when the state matrix itself is incomplete.