What is choosing-what-to-test?

A guide for deciding which Android behaviors belong in a test suite. It groups behavior by the kind of state it changes, such as screen state, in-memory ViewModel state, or saved data.

Use it to choose what to test in a module, find missing edge cases, or decide whether a ViewModel, Repository, or Compose UI needs coverage.

It helps teams spend testing effort on business behavior instead of writing tests for Android framework entry points such as Activities, Fragments, or Services.

choosing-what-to-test — Skill for Claude Code and Codex by skydoves

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add skydoves/android-testing-skills --skill choosing-what-to-test

Clone the repo

git clone --depth 1 https://github.com/skydoves/android-testing-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/skydoves/android-testing-skills/choosing-what-to-test/github.svg)](https://agentmods.dev/skills/skydoves/android-testing-skills/choosing-what-to-test)

Your own site

<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/choosing-what-to-test"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/choosing-what-to-test/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/choosing-what-to-test"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/choosing-what-to-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 175 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,191 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00175	$0.04191
Opus 5	$0.00088	$0.02096
Sonnet 5	$0.00035	$0.00838
Haiku 4.5	$0.00017	$0.00419

Measured 10d ago against content hash cf90b6cb402c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

choosing-what-to-test scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

fundamentals/concepts/choosing-what-to-test/SKILL.md · 283 lines

How it starts

The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

A module with at least one ViewModel, repository, or screen.
Familiarity with the Android architecture layers (UI / Domain / Data) so the agent can map "data layer" to a real path.
The 3-layer pyramid framing from ../understanding-the-testing-pyramid/SKILL.md.

Five categories of state to cover

The five state categories below are the synthesis the user asked for. They map onto the verbatim sections of developer.android.com/training/testing/fundamentals/what-to-test (the page itself uses layer-style headers — "Essential unit tests", "UI tests", "Testing Edge Cases" — but the underlying axis is what kind of state changes).

Read the full file on GitHub · 283 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 283 lines · 175 tokens per session scan A cf90b6cb402c

Subscribe to this mod's changes

choosing-what-to-test is a skill published in the GitHub repository skydoves/android-testing-skills (319 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 175 tokens to every session and 4,191 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

choosing-what-to-test