Android testing unit

Skill krutikJain/android-agent-skills/.github/skills/android-testing-unit

Android skills repository for Kotlin, Compose, XML, testing, CI, release work, and legacy upgrades

Install

npx -y skills add krutikJain/android-agent-skills --skill android-testing-unit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Write fast, focused Android unit tests for reducers, use cases, repositories, and lifecycle-safe state holders.

SKILL.md

3.5 KB, 591 tokens by cl100k_base, as published. Nobody here has run it

Android Testing Unit

When To Use

Use this skill when the request is about: android unit test strategy, test viewmodel reducer android, repository unit tests android.
Primary outcome: Write fast, focused Android unit tests for reducers, use cases, repositories, and lifecycle-safe state holders.
Handoff skills when the scope expands:
android-testing-ui
android-ui-states-validation

Workflow

Scope the risk surface: correctness, security, performance, test depth, or release automation.
Pick the narrowest verification strategy that still catches the likely regressions.
Instrument the workflow so failures are actionable rather than just red.
Run the relevant checks on the showcase apps and packaging outputs.
Capture any residual risk with explicit follow-up work and owner skills.

Guardrails

Prefer reproducible checks in CI over one-off local heroics.
Fail with a precise remediation path instead of a vague quality gate.
Keep secrets, signing material, and production credentials out of examples and fixtures.
Treat performance and security work as engineering tasks with evidence, not folklore.

Anti-Patterns

Adding more tests without increasing signal.
Shipping benchmarks or security scans that no one can reproduce.
Hard-coding release credentials into build logic.
Using synthetic metrics with no user-impact interpretation.

Examples

Happy path

Scenario: Cover reducer and formatter logic in both fixture apps with focused local tests.
Command: cd examples/orbittasks-compose && ./gradlew :app:testDebugUnitTest && cd ../orbittasks-xml && ./gradlew :app:testDebugUnitTest

Edge case

Scenario: Mock sync failures and permission-denied branches without instrumentation.
Command: cd examples/orbittasks-compose && ./gradlew :app:testDebugUnitTest

Failure recovery

Scenario: Separate unit-testing requests from UI testing or general architecture cleanup.
Command: python3 scripts/eval_triggers.py --skill android-testing-unit

Done Checklist

The implementation path is explicit, minimal, and tied to the right Android surface.
Relevant example commands and benchmark prompts have been exercised or updated.
Handoffs to adjacent skills are documented when the request crosses boundaries.
Official references cover the chosen pattern and the main migration or troubleshooting path.