Skip to content
TrustedSkillsbeta
Back to all skills

Qa Testing Android

Listed
vasilyu1983·vlatest·testing·MIT

Automates Android app QA testing via UI interactions, data validation, and report generation using intelligent scripting.

Repository

Install on your platform

This skill no longer installs under the name qa-testing-android. vasilyu1983/ai-agents-public is deleted or private, so it cannot be installed from.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

vasilyu1983

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

Nobody has reviewed this code. TrustedSkills indexes and links skills; it does not audit, run or scan them. A skill runs with whatever access you give your agent — read the source before you install it.

Automated safety checks

scanned

We could not read this skill's source, so none of the checks below were run.

Not scanned. none of the 98 skills in the repository match this slug — it was most likely renamed or removed upstream after the registry indexed it Source recorded as vasilyu1983/ai-agents-public.
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

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.