android-testing

You can write unit tests for Android ViewModels and Repositories by structuring tests to isolate business logic and data interactions. This enables fast feedback on your core app modules without requiring full device instrumentation.

Integration tests using MockWebServer provide the best way to test Room DAOs and Retrofit interactions. This approach validates end-to-end data flows and database operations within modern Android modules.

To set up Hilt testing, configure test graphs to validate dependency injection within your Android app. This ensures your Hilt integration correctly provides dependencies across unit and integration test layers.

You can use Roborazzi for screenshot testing Compose UIs to guard against visual regressions. It captures and verifies UI appearances, ensuring your Compose components render correctly across changes.

You need to configure Gradle specifically for Android integration and unit tests to specify dependencies and structure test layers. Proper Gradle setup enables isolated unit tests and end-to-end style verification.

Use screenshot tests over unit tests when you need to guard visual regressions in Compose UIs rather than verifying isolated business logic. Unit tests provide fast feedback on ViewModels, while screenshot tests verify appearance.