testing-setup

To set up Android testing infrastructure, the skill inspects your project's dependency and config files to determine if the app uses Compose, Views, or a hybrid architecture, then recommends and installs the appropriate test frameworks and runners.

The best way to structure unit tests and behavior UI tests is to refactor code for testability using fakes and dependency injection, placing tests in the correct source sets like `test` and `androidTest` based on the applied testing strategy.

You add screenshot tests and end-to-end journeys by installing the right test frameworks and rules, configuring the `screenshotTest` source sets, and setting up navigation and deeplink test suites alongside state restoration verification.

Yes, the testing strategy supports Jacoco coverage and device simulation by including quality guardrails that set up coverage tracking, device and window-size simulation, and state restoration verification within the test infrastructure.

Yes, you can use dependency injection to refactor an Android project for UI testability by replacing real dependencies with fakes and configuring testing rules to isolate UI components and behavior tests effectively.

The Android testing setup generates a Markdown report deliverable documenting the analysis of your current testing stack and detailing the applied changes to your test infrastructure, source sets, and frameworks.