applying-testing-strategies

What problem does it solve?

This skill helps you structure Android test suites so they scale reliably, stay readable, and avoid common CI-only failures caused by flakiness, time, concurrency, or external state.

Core Features & Use Cases

• Test structure & naming: Establishes a consistent Given-When-Then flow and a readable test method naming convention for faster debugging.
• Determinism & hermeticity guidance: Provides a checklist for eliminating sources of non-determinism like time, coroutines, animation timing, randomness, and external dependencies.
• Hilt-based dependency replacement: Explains how to correctly use @HiltAndroidTest, HiltAndroidRule, and the module replacement APIs (@TestInstallIn, @UninstallModules, @BindValue), including rule ordering and inject() requirements.
• Source-of-truth mapping: Clarifies which guidance belongs to strategies vs stability vs Hilt testing so you don’t misattribute recommendations.

Quick Start

Use the applying-testing-strategies skill to rewrite your Android test class to follow Given-When-Then, remove flake sources, and correctly apply Hilt replacement with deterministic rule ordering.