android-testing
Write unit tests, Compose UI tests, and Hilt-integrated tests for Android. Use when writing test files or testing ViewModels, Composables, or Repositories with MockK and coroutine test utilities.
69
Quality
—
Does it follow best practices?
Impact
—
No eval scenarios have been run
Securityby
Passed
No known issues
Android Testing Standards
Priority: P0
Implementation Guidelines
Unit Tests
- Scope: ViewModels, Usecases, Repositories, Utils.
- Coroutines: Use
runTest(kotlinx-coroutines-test). UseMainDispatcherRuleto 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
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
611f52a
- Last updated
- Created
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.