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.
npx skills add noloman/Android-AI-skills --skill android-testing-best-practicesgit clone --depth 1 https://github.com/noloman/Android-AI-skillsWrote 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.
[](https://agentmods.dev/skills/noloman/android-ai-skills/android-testing-best-practices)<a href="https://agentmods.dev/skills/noloman/android-ai-skills/android-testing-best-practices"><img src="https://agentmods.dev/badge/skills/noloman/android-ai-skills/android-testing-best-practices/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.
<a href="https://agentmods.dev/skills/noloman/android-ai-skills/android-testing-best-practices"><img src="https://agentmods.dev/badge/skills/noloman/android-ai-skills/android-testing-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00343 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
android-testing-best-practices 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 9d 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.
What it actually says
name: android-testing-best-practices description: Android testing best practices — Compose UI testing, screenshot tests, Room migrations, CI. user-invocable: true
Android Testing Best Practices
Cross-cutting skill — always activates alongside the project-type-specific skill.
Hard Rules
- Follow the test pyramid — many unit tests, fewer integration, fewest E2E.
- Use Compose testing APIs for Compose UI — not Espresso on Compose.
- Prefer fakes over mocks for dependencies.
- Export Room schemas (exportSchema = true) and test all migrations.
- Use descriptive test names that state the scenario and expected outcome.
- No Thread.sleep() in tests — use idling resources or test coroutine control.
- Tests must be deterministic — no flaky randomness or timing dependencies.
- Unit tests run on every PR.
- Use TestDispatcher + runTest for coroutine tests.
- Quarantine flaky tests — do not let them block the pipeline.
Core Patterns
- One concept per test — single assertion focus.
- AAA structure (Arrange, Act, Assert) in every test.
- Use test data builders or fixtures, not inline object construction.
- Test all UI states: loading, content, error, empty.
- Use Robolectric for fast on-JVM Android tests when instrumented tests aren't needed.
- Separate test source sets: test/ (unit), androidTest/ (instrumented).
References
- references/compose_ui_testing.md
- references/screenshot_testing.md
- references/instrumented_testing.md
- references/room_migration_testing.md
- references/test_architecture.md
- references/ci_testing.md
- references/test_fixtures.md
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 40 lines · 0 tokens per session scan A 8632d8da2d50
android-testing-best-practices is a skill published in the GitHub repository noloman/Android-AI-skills (6 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 343 tokens. 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-31.
Other skills, from other repositories
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
eas-simulator
EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…