android-ci-tests

Generate a GitHub Actions workflow for Android unit, lint, and instrumented tests.

3|1|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/hitoshura25/claude-devtools --skill android-ci-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-ci-tests
Source: https://github.com/hitoshura25/claude-devtools/tree/main/skills/android-ci-tests
Command: npx skills add https://github.com/hitoshura25/claude-devtools --skill android-ci-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android projects often struggle with reliable, fast feedback during development due to misconfigured CI pipelines. This Skill provides a ready-to-use GitHub Actions workflow that standardizes unit, lint, and instrumented testing across projects.

Core Features & Use Cases

  • Separate jobs for unit tests, lint, and instrumented tests to parallelize and organize CI
  • Full environment setup including JDK 17, Gradle cache, Android SDK setup, and AVD caching to speed up runs
  • Pinned Actions SHAs and a single source of truth workflow at .github/workflows/test.yml
  • Upload test results and artifacts to preserve feedback across jobs
  • Use Case: Ensure reliable Android CI for feature branches and PRs, validating tests before merging

Quick Start

Use the android-ci-tests skill to generate the CI workflow at .github/workflows/test.yml in your repository.

Frequently Asked Questions about android-ci-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up GitHub Actions for Android unit tests and lint checks?

Setting up GitHub Actions for Android CI involves creating a workflow at .github/workflows/test.yml that runs separate jobs for unit tests, lint checks, and instrumented tests to parallelize feedback across pushes and PRs.

Does this Android CI workflow cache Gradle and Android SDK dependencies to speed up runs?

Yes, the Android CI workflow caches Gradle dependencies, sets up the Android SDK, and uses AVD caching to speed up runs. This ensures fast and reliable feedback during development.

Can I use this GitHub Actions workflow to run Android instrumented tests?

Yes, you can run Android instrumented tests with this GitHub Actions workflow. It includes a dedicated job for instrumented tests alongside unit tests and lint checks, with full environment setup including JDK 17.

Do I need JDK 17 to run Android tests in CI with this workflow?

Yes, you need JDK 17 to run Android tests in CI with this workflow. The workflow enforces JDK 17 setup as part of the full environment configuration to ensure compatibility and reliable test execution.

Why should I pin GitHub Actions SHAs in my Android CI workflow?

Pinning GitHub Actions SHAs in your Android CI workflow enhances security by preventing unauthorized changes. This workflow enforces pinned action SHAs to maintain a secure and reliable testing pipeline.

What is the best way to organize Android CI jobs for parallel test execution?

The best way to organize Android CI jobs for parallel test execution is using separate jobs for unit tests, lint, and instrumented tests. This workflow structure parallelizes runs and uploads test results as artifacts to preserve feedback.