choosing-what-to-test
choosing-what-to-test is a Test strategy & case design skill for AI agents, published by skydoves in the android-testing-skills repository on GitHub. Skillspace rates choosing-what-to-test C (71/100) and it passed the safety scan; the rating is based on static analysis only.
Use this skill to pick which behaviors to cover in an Android test suite using Google's five-category state vocabulary plus the explicit "what NOT to test" list from `/training/testing/fundamentals/what-to-test`. Covers state on screen, state held in memory (ViewModels), persisted state (DB / DataStore / files), other state (system bars / system services), and errors / edge cases. Includes Google's verbatim "Tests to Avoid" list (framework entry points such as activities / fragments / services should not have business logic) and an edge-case mining checklist. Use when the user asks "what should I write tests for", "should I unit-test this Activity", "do I need a test for this util class", "what edge cases am I missing", or "should I test the ViewModel or the Composable".
- Grade
- C
- Quality
- 71 / 100
- Safety
- Passed
- GitHub stars
- 296
Unproven: rated by static analysis only, not yet compared head-to-head.
This rating describes the version of the repository we crawled; it may have changed since, so go by its current files.
Our review
- Architecture
- 94 / 100
- Maturity
- Basic: a single SKILL.md
- Security scan
- No issues found
- License
- Apache-2.0
- Adoption
- Adopted by 1 other repositories, in 0 collections
Not checked yet
- Not judged on the rubric yet (not a contender in its category)
- No blind task eval yet
- Scope (portable / vendor / repo-internal) not assessed; only the top of each category is read for scope
- Sibling files (scripts, references) not fetched; security scan covers SKILL.md only
Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.