kotlin-testing-kmp

Structure Kotlin Multiplatform unit tests by placing shared logic validations in commonTest using kotlin.test, then expanding coverage with platform-specific tests as your project grows to maintain a proper test pyramid.

Robolectric and instrumented tests in Kotlin Multiplatform require clear separation of concerns, using Robolectric for local Android-specific validations and instrumentation for broader platform checks to keep shared logic maintainable.

Yes, Compose Multiplatform UI testing supports cross-target mappings that keep shared logic testable, ensuring UI tests remain stable and maintainable across the platforms your project targets.

Organize tests by enforcing a practical test pyramid: validate core shared logic in commonTest with kotlin.test, then carefully extend with Robolectric, instrumented, and UI tests for platform-specific layers.

You need instrumented tests instead of local unit tests in Kotlin Multiplatform when performing platform-specific validations that require an actual device or emulator environment to accurately verify target behavior.

Your test pyramid struggles because balancing fast local tests with platform-specific validations in Kotlin Multiplatform is difficult; enforcing kotlin.test in commonTest and separating Robolectric tests stabilizes shared logic.