testing-setup
Analyze and create a testing strategy for Android apps - install testing libraries, set up test infrastructure, create harnesses for unit tests, UI tests, screenshot tests, and end-to-end tests.
Install
With your agent
Install OMGSkills skill "android/skills:testing-setup" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/android/skills /tmp/skills && ln -s /tmp/skills/testing/testing-setup ~/.claude/skills/testing-setupFrom README
Step 1: Analyze the current testing To understand the testing of an existing project, look for these dependencies in the libs.versions.toml file, or build files: Dependency Injection framework used. For example, Hilt, Koin, Anvil, or vanilla Dagger. Unit (local) testing framework this project uses. For example, JUnit4 or JUnit5. Mocking framework (if any) used for unit tests, and for instrumented and UI tests. For example, Mockito or Mockk. Robolectric. Identify which of these three uses apply: Used in unit tests to have fakes for platform entities To run behavior UI tests without a device or emulator. For example, used to run Espresso or Compose tests. To do screenshot testing with Roborazzi Is the app 100% Compose, Views or hybrid? Behavior UI tests: Compose Tests (androidx.compose.ui:ui-test-) Espresso Tests for Views. Check for wrappers such as Kaspresso. Dependencies: androidx.test.espresso:espresso-core, androidx.test:runner, androidx.test:rules. Screenshot tests.
More from this repo
android-cli
Provides instructions for installing and using the `android` CLI.
android-intent-security
Best practices for Android Intent security.
navigation-3
Learn how to install and migrate to Jetpack Navigation 3, and how to implement features and patterns such as deep...