android-testing

To coordinate Android tests, you need a strategy that selects the right test type for each code path. Use JVM unit tests for logic validation and instrumented tests when platform behavior matters, ensuring full coverage across devices.

Use testDebugUnitTest to validate pure logic paths on the JVM, and switch to connectedDebugAndroidTest when you need to verify platform-specific behavior across physical devices or emulators to catch device-level regressions.

Compose UI tests validate your user interface components by executing them within the Android test ecosystem. A coordinated strategy helps plan, execute, and verify these UI tests alongside your unit and instrumented tests.

Robolectric is supported for running Android unit tests directly on the JVM. It allows you to execute tests that normally require an Android environment without needing a physical device or emulator setup.

Testing Room migrations requires validating database schema changes across versions. A coordinated test strategy includes verifying these migrations to ensure data integrity is maintained when users update your application.

Testing coroutines in Android requires validating asynchronous code paths across your project. A coordinated strategy integrates coroutine testing within your JVM unit tests and instrumented tests to verify concurrent logic safely.