Android
Room is Android's recommended database library, wrapping SQLite with type-safe query builders and Kotlin coroutines support. Testing Room properly means validating DAO queries, schema migrations, and Paging 3 integration—without ever touching a real disk database. Room Testing Strategy Room provides first-class support for testing through in-memory databases:
Android
Kotlin Flow is the standard for reactive programming in Android—but testing asynchronous streams is notoriously awkward. Turbine is Cash App's library that makes Flow testing readable and deterministic. Instead of manual coroutine collection and timing hacks, you get clean, sequential assertions. Why Testing Flows Is Hard Without
Android
Koin is the lightweight dependency injection framework that dominates Android Kotlin projects. Unlike Dagger/Hilt which uses code generation, Koin operates at runtime—which means misconfigured modules fail at startup rather than compile time. Testing your Koin setup properly catches these failures before they hit production. Why Koin Testing Matters
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. Unlike Retrofit, which wraps OkHttp, Ktor has its own engine abstraction that makes testing particularly clean: just swap the real engine for MockEngine and control every response. Why Ktor Testing
Android
Jetpack Compose replaces the View hierarchy with a declarative composable tree—and that changes how you test Android UIs. Traditional Espresso tests targeting View IDs don't work. Instead, Compose provides a dedicated testing API built around the semantic tree, enabling more robust and readable tests that aren'
Testing
TalkBack is Android's built-in screen reader, and testing it manually doesn't scale across a large test suite. Espresso's AccessibilityChecks API, the Accessibility Test Framework, and Robolectric together give you a layered approach to catching accessibility regressions in CI before they reach users. Android'
Testing
WCAG 2.1 was the first version of the Web Content Accessibility Guidelines to explicitly address mobile. Applying it to native iOS and Android apps requires mapping each criterion to platform-specific implementation patterns and choosing the right automated tools for coverage. This guide gives you the full picture. WCAG 2.
Testing
Meta Quest runs Android under the hood, which means your Android testing toolchain — ADB, Appium, logcat, am instrument — works on Quest with some configuration. This guide covers device setup, Appium with UiAutomator2 for Quest UI automation, OVR Metrics for performance testing, and running Unity tests directly on device. Meta Quest
Testing
Android testing is layered. Your app has units of business logic, UI components that respond to state, and end-to-end flows that span multiple screens. Each layer needs a different kind of test. This guide covers the full Android testing stack: unit tests, integration tests, and UI tests — when to use
Testing
Espresso is Google's official UI testing framework for Android. Unlike Appium, which runs as an external server, Espresso runs inside the app process. This makes it significantly faster and more reliable — no network overhead, no timing guesses, no session management. If you're testing a native Android