android-testing

Unit tests for Android ViewModels use JUnit5 as the test framework, MockK to mock dependencies, and Turbine to assert Flow emissions. This stack enables isolated testing of ViewModel logic without Android framework dependencies, improving test speed and reliability.

Turbine is a testing library designed for Flow testing that provides a simple API to assert emitted values. Combined with kotlinx-coroutines-test, it enables reliable coroutine testing across ViewModel, UseCase, and repository layers without flaky timing issues.

Compose UI testing uses dedicated Compose testing APIs integrated into JUnit5 test suites. Patterns differ from traditional views but follow the same MockK and Turbine approaches for testing logic layers, providing consistency across unit, UI, and integration tests.

Testing patterns cover all three layers: domain layer uses UseCase tests with MockK, presentation layer tests ViewModels with Turbine for Flows, and data layer tests repositories with mocked dependencies. Templates and naming conventions ensure consistency and maintainable coverage targets.

JUnit5 integrates with Hilt through test annotations and setup snippets provided in templates. This Skill covers Hilt integration patterns to enable dependency injection in test environments while maintaining isolation through MockK.