android-e2e-testing-setup_skill

Overview

This skill sets up a lightweight UI Automator 2.4 smoke test to verify your Android app launches without crashing. It supports both debug and release builds because UI Automator interacts with the app externally and does not require debuggable APKs. The goal is fast validation of app startup and basic UI presence, useful for local checks and CI release validation.

How this skill works

It adds UI Automator 2.4 and AndroidX test dependencies, provides a compact SmokeTest using the modern uiAutomator { } DSL, and includes helpers to handle common permission flows like HealthConnect. You run tests with connectedAndroidTest/connectedDebugAndroidTest (or configure testBuildType = "release" to validate release APKs). Tests require a connected device or emulator and use built-in waiting and safe null handling to assert the app is visible.

When to use it

• Validate app launches locally before a release
• Catching ProGuard/R8 issues by running tests against release APKs
• Quick sanity checks in CI pipelines
• Verify runtime permission flows and basic UI visibility
• Smoke testing after installing a new build on a device

Best practices

• Ensure minimum SDK >= 21 and a connected device/emulator before running tests
• Replace {PACKAGE_NAME} in the test with your app's applicationId from build.gradle or AndroidManifest
• Use testBuildType = "release" only for release validation when release signing is configured
• Keep tests focused and fast — smoke tests should only assert launch and visible UI, not full UX flows
• Handle known permission dialogs explicitly (example includes HealthConnect and runtime permissions)

Example use cases

• Local verification that an app launches on an emulator after a new commit
• CI step to run smoke tests against signed release APKs to detect ProGuard regressions
• Pre-release validation on a physical device to ensure no startup crashes
• Automated sanity check after installing nightly builds on test devices