Choosing What to Test — Cover State, Skip Framework Entry Points

Android test suites under-cover business logic and over-cover framework glue. Google's /training/testing/fundamentals/what-to-test page sorts test value by what state the code touches and explicitly names the categories of tests to avoid. This skill encodes those categories and the edge-case checklist so the agent can advise concretely instead of saying "test everything important".

When to use this skill

• The user asks "what should I write tests for in this module" or "do I need a test for X".
• The user asks whether to unit-test an Activity, Fragment, or Service (answer: usually no — see "What NOT to test").
• The user is reviewing a PR and the test gap is unclear.
• The user asks "what edge cases am I missing for this function".
• The user asks where the testing effort should land between ViewModel, Repository, and Composable.

When NOT to use this skill

• The user already knows what to test and is choosing the test scope (small/medium/big) — use ../understanding-the-testing-pyramid/SKILL.md.
• The user is choosing between fakes / mocks / stubs — use ../../doubles/picking-test-doubles/SKILL.md.
• The user is wiring source sets (src/test/ vs src/androidTest/) — use ../../strategies/organizing-test-source-sets/SKILL.md.

Prerequisites