choosing-what-to-test

Android ViewModel and repository testing strategy requires distinguishing high-value business logic from framework-specific behaviors. Categorize screen state, memory state, and persisted data to identify critical test cases while avoiding boilerplate code.

Android testing should avoid testing framework entry points like Activities and Fragments, as well as third-party library internals. Avoiding these low-value framework-level tests prevents over-testing boilerplate code and keeps your test suite fast, reliable, and maintainable.

Android instrumented tests are needed when verifying framework-specific behaviors and system services, whereas unit tests suit pure business logic. Apply a state-based coverage framework to screen state and persisted data to determine the correct test type.

State-based coverage strategy effectively targets Android edge cases by categorizing screen state, memory state, persisted data, and system services. This framework ensures critical edge cases receive appropriate unit or instrumented test coverage based on their architectural layer.

This Android testing strategy strictly adheres to Google's testing fundamentals by prioritizing high-value business logic tests and explicitly avoiding testing framework entry points or third-party library internals. It ensures your test suite remains fast, reliable, and maintainable.