android-testing

To test StateFlow emissions in Android ViewModels, use Turbine alongside UnconfinedTestDispatcher to verify loading states and one-time event emissions predictably without flaky behavior.

The best way to write Compose UI tests for multi-screen flows is using the Robot pattern with ComposeTestRule, which simplifies complex multi-step end-to-end user interactions into maintainable test scripts.

To set up JUnit5 for Kotlin Multiplatform testing, apply standardized configurations for JUnit5, Turbine, AssertK, and UnconfinedTestDispatcher to streamline coroutine and StateFlow testing across platforms.

You should use fake repositories instead of mocks for data layer unit tests because reusable in-memory fake implementations eliminate brittle mocks, creating more reliable and maintainable test setups.

Yes, you can use this Android testing approach for Kotlin Multiplatform apps, as the standardized patterns for JUnit5, Turbine, and fake repositories are designed to support KMP applications directly.

To instantiate SavedStateHandle in ViewModel unit tests, use the provided standardized patterns for SavedStateHandle test instantiation to verify state preservation logic without repetitive boilerplate.