android-e2e-testing-setup

Automate Android app launch validation with UI Automator 2.4 smoke tests.

3|1|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/hitoshura25/claude-devtools --skill android-e2e-testing-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-e2e-testing-setup
Source: https://github.com/hitoshura25/claude-devtools/tree/main/skills/android-e2e-testing-setup
Command: npx skills add https://github.com/hitoshura25/claude-devtools --skill android-e2e-testing-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates validation of Android app launches to detect crashes and ensure stability across builds, reducing flaky launches and manual QA effort.

Core Features & Use Cases

  • UI Automator 2.4 smoke test: lightweight check to verify app launches and basic UI responsiveness.
  • Permissions handling: guidance for HealthConnect and runtime permission prompts to prevent test stalls.
  • Cross-build validation: works with both debug and release builds to aid release validation and continuous QA.

Quick Start

Install the Android project, ensure a device or emulator is available, configure dependencies as described, and run connected Android tests with Gradle: ./gradlew connectedDebugAndroidTest

Frequently Asked Questions about android-e2e-testing-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Android app launch testing to detect crashes?

Automate Android app launch testing by running UI Automator smoke tests via Gradle to validate basic UI responsiveness and detect crashes. This checks app launch stability across debug and release builds, reducing manual QA effort.

How do I handle HealthConnect permissions in UI Automator tests?

Handle HealthConnect permissions in UI Automator tests by configuring runtime permission prompts to prevent test stalls. This Skill provides guidance for managing these prompts so your smoke tests run without hanging on permission dialogs.

Do I need a connected device or emulator for instrumented testing with Gradle?

Yes, instrumented testing requires a connected device or emulator. You must have a device or emulator available and run the Gradle command connectedDebugAndroidTest to execute the UI Automator smoke tests.

Can I validate release builds with UI Automator smoke tests?

Yes, UI Automator smoke tests support cross-build validation for both debug and release builds. This aids release validation and continuous QA by ensuring app launch stability across different build configurations.

What's the best way to run a smoke test for Android app launch stability?

The best way to run a smoke test for Android app launch stability is using UI Automator 2.4 within a Gradle-based Android project. Execute ./gradlew connectedDebugAndroidTest to verify app launches and basic UI responsiveness.

Why does my connectedDebugAndroidTest stall during Android instrumented testing?

Your connectedDebugAndroidTest may stall during Android instrumented testing due to unhandled runtime permission prompts. Properly configuring HealthConnect and runtime permissions prevents test stalls and allows the smoke tests to complete.