Testing
PITest (PIT) is the dominant mutation testing framework for JVM languages. While most documentation targets Maven/Java setups, PITest works equally well with Gradle and Kotlin — with a few configuration differences worth knowing about. This guide covers the complete Gradle setup, Kotlin-specific behavior, and how to get meaningful results
Testing
ViewModels are the core of Android architecture: they hold state, handle business logic, and expose data via Kotlin Flow.
Kotlin
Unit tests tell you your logic is correct. Espresso tests tell you your UI actually works on a real Android device.
Android
Room is Android's recommended database library, wrapping SQLite with type-safe query builders and Kotlin coroutines support.
Android
Kotlin Flow is the standard for reactive programming in Android—but testing asynchronous streams is notoriously awkward.
Android
Koin is the lightweight dependency injection framework that dominates Android Kotlin projects.
Android
Retrofit is Android's de facto HTTP client library. Testing it properly means validating that your API service interfaces produce correct requests, handle error responses gracefully, and work with your custom call adapters and interceptors. OkHttp's MockWebServer is the tool that makes all of this possible. Why
Android
Ktor is JetBrains' official HTTP client for Kotlin Multiplatform—used in KMP projects, pure JVM backends, and Android applications.
Android
Jetpack Compose replaces the View hierarchy with a declarative composable tree—and that changes how you test Android UIs.
Testing
Android's TalkBack screen reader serves millions of users who depend on it for daily app interaction.
Testing
Compose Multiplatform extends Jetpack Compose beyond Android, bringing the same declarative UI model to iOS, desktop (macOS, Windows, Linux), and web.
Testing
Kotlin Multiplatform (KMP) lets you write business logic once and share it across Android, iOS, desktop, and web.