What problem does it solve? Setting up a complete Android testing strategy requires choosing and wiring many frameworks (JUnit, Robolectric, Espresso, Compose Test, Hilt testing, screenshot tools, JaCoCo), which is error-prone and time-consuming when done manually. ## Core Features & Use Cases - Testing Stack Analysis: Inspects libs.versions.toml and build files to detect existing DI, mocking, UI testing, and screenshot frameworks, then generates a Markdown report. - Framework Installation & Configuration: Installs JUnit4, JaCoCo, Robolectric, Compose Preview Screenshot Testing, Dropshots, UI Automator, and configures Hilt test runners and rules. - Test Authoring Guidance: Creates unit tests for ViewModels and repositories, Compose/Espresso behavior tests, navigation tests, database tests with in-memory SQLite, and screen-level screenshot tests across sizes and themes. - Use Case: Point the Skill at an Android project with no tests and receive a configured testing infrastructure plus a documented testing strategy in docs/testing.md or AGENTS.md. ## Quick Start Analyze this Android project's testing setup and install a complete unit, UI, and screenshot testing infrastructure.