mobile-testing

Unit testing Android ViewModels requires JUnit5, MockK for mocking dependencies, and Turbine for testing coroutine flows. This Skill provides reusable patterns that standardize ViewModel test scaffolding, ensuring consistent setup across your codebase and deterministic test execution.

Compose testing uses dedicated testing libraries alongside JUnit5 to verify UI behavior. This Skill supplies structured patterns for Compose UI tests that integrate with your existing unit test framework, enabling reliable verification of UI components and user interactions.

Yes. JUnit5 and MockK work together effectively for Android integration tests. This Skill provides tested patterns combining both tools with Turbine for flow testing across Repository and ViewModel layers, ensuring comprehensive coverage from business logic to data access.

Repository testing with coroutines and flows requires Turbine to emit and assert on flow values. This Skill includes Repository test patterns using Turbine alongside JUnit5 and MockK, standardizing how to validate async data operations across your modules.

No. This Skill provides a reusable pattern set designed for quick adoption across new modules. Once you add the standard dependencies (JUnit5, MockK, Turbine, Compose testing) to build.gradle.kts, you can apply consistent test patterns to ViewModels, Repositories, and Compose UIs without reconfiguration.

MockK excels at mocking Kotlin code and coroutine dependencies but requires careful setup for Android framework classes. This Skill's patterns focus on testable architecture—mocking business logic and data layers—to avoid framework mock complexity and ensure deterministic, maintainable tests.