Agent Skills
› midudev/autoskills
› android-testing-unit
android-testing-unit
GitHub用于编写快速聚焦的Android单元测试，覆盖reducer、用例、仓库及状态持有者。指导用户通过界定风险范围、选择验证策略和配置CI流程来确保测试有效性，避免反模式，并提供具体执行命令与官方参考文档。
Trigger Scenarios
android unit test strategy
test viewmodel reducer android
repository unit tests android
Install
npx skills add midudev/autoskills --skill android-testing-unit -g -y
SKILL.md
Frontmatter
{
"name": "android-testing-unit",
"metadata": {
"tags": [
"android",
"testing",
"unit-tests",
"verification"
],
"owners": [
"@android-agent-skills\/maintainers"
],
"version": "0.1.0",
"category": "quality-release",
"triggers": {
"exclude": [
"ui screenshot only",
"play store listing",
"apk alignment"
],
"include": [
"android unit test strategy",
"test viewmodel reducer android",
"repository unit tests android",
"mock coroutine dependency android",
"fast test coverage android"
]
},
"test_targets": [
"examples\/orbittasks-compose",
"examples\/orbittasks-xml",
"benchmarks\/triggers.jsonl"
]
},
"description": "Write fast, focused Android unit tests for reducers, use cases, repositories, and lifecycle-safe state holders."
}
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-uiandroid-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.
Official References
Version History
- 0ec7253 Current 2026-07-24 20:51
