android-testing

Use testDebugUnitTest for local JVM unit tests when behavior is platform-independent, and connectedDebugAndroidTest for instrumented tests requiring a connected device or emulator. Selecting the correct Android testing strategy prevents late-stage regressions by validating platform-dependent code accurately.

Compose UI testing is handled by selecting the correct instrumented test strategy to verify UI behavior on an emulator or device. This approach ensures your Compose UI components function correctly by validating user interactions and visual states through connected device execution.

Room migration testing validates database schema changes by running instrumented tests on a connected device. This ensures your Room migrations preserve existing data and maintain database integrity across version updates without introducing runtime failures.

Coroutine testing can be performed using local JVM unit tests when the tested logic is platform-independent. This allows you to verify asynchronous behavior and data flows quickly without needing an emulator or connected device execution.

Fixing failing Android tests requires identifying the correct test type, whether JVM unit or instrumented, and implementing the specific test cases needed. This approach validates outcomes by applying the right test strategy and reporting emulator execution status as evidence.

Yes, instrumented tests require a connected emulator or physical device to execute. The testing strategy explicitly notes when emulator or device verification was not run, ensuring you maintain evidence-focused verification for platform-dependent Android behavior.