android-testing

name	android-testing
description	Write Android unit, Compose UI, and Hilt-integrated tests. Use when designing test behavior with MockK or coroutine test utilities; defer database/WorkManager-specific recipes to the owning feature skill.
metadata	{"triggers":{"files":["**/*Test.kt","**/*Rule.kt"],"keywords":["@Test","runTest","composeTestRule","HiltAndroidTest","MockK","createAndroidComposeRule","MainDispatcherRule","@TestInstallIn"]}}

Android Testing Standards

Priority: P0 (CRITICAL)

Implementation Guidelines

Unit Tests

• Scope: ViewModels, Usecases, Repositories, Utils.
• Coroutines: Use runTest (kotlinx-coroutines-test). Use MainDispatcherRule to mock Main dispatcher.
• Mocking: Use MockK.

UI Integration Tests (Instrumentation)

• Scope: Composable Screens, Navigation flows.
• Rules: Use createAndroidComposeRule + Hilt (HiltAndroidRule).
• Isolation: Fake repositories in DI modules (@TestInstallIn).

Anti-Patterns

• No Real Network in Tests: Always mock with MockK or fake repositories via @TestInstallIn.
• No Thread.sleep: Use IdlingResource or composeTestRule.waitUntil for async timing.

References

• Test Rules