Can I test release builds with this setup?

Yes, the skill provides an optional configuration to set the test build type to release, allowing you to catch issues related to code shrinking and obfuscation.

Does this skill require a physical device?

It requires either a physical Android device with USB debugging enabled or a running emulator to execute the instrumented tests.

How does it handle Android permissions?

The generated test includes specialized helper functions to automatically navigate and accept common runtime permissions and multi-step HealthConnect permission flows.

What version of UI Automator is used?

This skill specifically implements UI Automator 2.4, which utilizes a modern Kotlin DSL for more readable and stable tests compared to previous versions.

Android E2E Testing Setup

Name: Android E2E Testing Setup
Author: hitoshura25

byhitoshura25

Mobile Development

Configures automated UI smoke tests using UI Automator 2.4 to validate Android app launches and stability across debug and release builds.

Acerca de

This skill automates the setup of an end-to-end (E2E) smoke testing suite for Android applications, leveraging the modern UI Automator 2.4 API. It streamlines the integration of necessary Gradle dependencies and generates a robust SmokeTest.kt template designed to verify app launches without crashes. A key advantage of this skill is its ability to test release builds, allowing developers to catch ProGuard or R8 obfuscation issues before deployment. It includes built-in logic for handling complex runtime permissions, such as HealthConnect, ensuring tests run smoothly in various environments.

Características Principales

Integrated HealthConnect and runtime permission handling logic
0 GitHub stars
Automated UI Automator 2.4 dependency configuration
Standardized verification via Gradle connected tests
Support for testing both debug and production/release builds
Generation of a modern Kotlin DSL smoke test template

Casos de Uso

Validating that a release build doesn't crash due to ProGuard/R8 rules
Setting up a quick smoke test suite for new Android projects
Automating permission dialog handling in CI/CD testing pipelines

Acerca de

Características Principales

Integrated HealthConnect and runtime permission handling logic
0 GitHub stars
Automated UI Automator 2.4 dependency configuration
Standardized verification via Gradle connected tests
Support for testing both debug and production/release builds
Generation of a modern Kotlin DSL smoke test template

Casos de Uso

Validating that a release build doesn't crash due to ProGuard/R8 rules
Setting up a quick smoke test suite for new Android projects
Automating permission dialog handling in CI/CD testing pipelines