Qa Testing Android

What it does

This skill automates Android application quality assurance (QA) testing using various frameworks including Espresso, UIAutomator, and Compose Testing. It allows an AI agent to execute tests, manage emulators and devices, install APKs, run unit and instrumented tests, and generate reports. The tool leverages Gradle for test execution and emphasizes stability through techniques like disabling animations and utilizing AndroidX Test Orchestrator.

When to use it

• Debugging or stabilizing flaky Android UI tests.
• Adding Espresso tests for View-based user interfaces.
• Creating Compose UI tests for composable elements.
• Implementing UIAutomator tests for system UI interactions or cross-app flows.
• Setting up an automated testing process within a CI/CD pipeline (Continuous Integration/Continuous Delivery).

Key capabilities

• Listing and managing Android emulators (emulator -list-avds, emulator @<avd_name>).
• Installing APKs on devices (adb install -r <path-to-apk>).
• Running unit tests (./gradlew test).
• Executing instrumented tests (connected and Gradle Managed Devices – GMD) (./gradlew connectedAndroidTest, ./gradlew <device><variant>AndroidTest).
• Clearing app data (adb shell pm clear <applicationId>).
• Utilizing AndroidX Test Orchestrator for test isolation.
• Employing Espresso for View-based UI testing.
• Using Compose Testing for composable UI testing.
• Leveraging UIAutomator for system and cross-app UI testing.

Example prompts

• "List available emulators."
• "Run the instrumented tests connected to my device."
• "Install the APK located at /path/to/my_app.apk."
• "Execute unit tests using Gradle."

Tips & gotchas

• For stable instrumented tests, ensure animationsDisabled = true is configured in your Gradle settings.
• Consider using Gradle Managed Devices (GMD) and ATD images for CI environments.
• Prioritize the use of IdlingResources or Compose idling + waitUntil over sleep calls to avoid timing issues during test execution.