mcpField
A
android-testing-unit

android-testing-unit

github.com/midudevTesting & quality7.0k60 installsUpdated 1w ago
Repository

About android-testing-unit

An Android testing skill for developers writing focused unit tests for reducers, use cases, repositories, and lifecycle-safe state holders. It guides test selection, actionable failure checks, and handoffs to UI testing when scope expands.

Key features

  1. 01Choose focused unit test strategies
  2. 02Test reducers and use cases
  3. 03Cover repositories and state holders
  4. 04Make failures actionable
  5. 05Hand off UI testing requests

Use cases

  1. 01Test reducer and formatter logic
  2. 02Mock sync failures and permission denials
  3. 03Separate unit tests from UI testing

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/midudev/autoskills --skill android-testing-unit

After installing, type/android-testing-unitin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
official-links.md
patterns.md
scenarios.md
scripts/
run_examples.sh

Details

From the project README

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

  1. Scope the risk surface: correctness, security, performance, test depth, or release automation.
  2. Pick the narrowest verification strategy that still catches the likely regressions.
  3. Instrument the workflow so failures are actionable rather than just red.
  4. Run the relevant checks on the showcase apps and packaging outputs.
  5. 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.

Official References

Comments

Markdown supported