Appium
WebdriverIO's Appium integration is the smoothest way to write mobile automation tests in JavaScript. The @wdio/appium-service handles starting and stopping Appium automatically, the configuration is declarative, and the same test code works against iOS and Android with minimal platform-specific branches. This guide covers setting up
Appium
Appium's XCUITest driver wraps Apple's XCUITest framework, which means iOS automation runs through the same testing infrastructure that Xcode uses natively. This gives you full access to iOS platform capabilities — but it also means understanding how WebDriverAgent (WDA) works and how to configure it correctly for
Appium
Simulators and emulators catch most bugs, but some issues — memory pressure, thermal throttling, hardware-specific rendering, carrier network behavior — only appear on real devices. Device farms give you access to hundreds of real iOS and Android devices without maintaining physical hardware. This guide covers running Appium tests on the three
Testing
ViewModels are the core of Android architecture: they hold state, handle business logic, and expose data via Kotlin Flow. Testing them thoroughly — including loading states, error handling, and side effects — requires understanding how to control coroutines and observe Flow emissions in tests. This guide covers ViewModel testing with TestDispatcher, Turbine
Mobile Testing
The pitch for Waldo is "mobile testing without writing code." The reality is close to that — but there are setup steps that aren't as obvious as the marketing makes them sound. This guide walks you through the actual setup process, what you'll need before
Game Testing
Releasing a game on PC, PlayStation, Xbox, iOS, and Android isn't five releases — it's five completely different QA challenges running in parallel. Platform-specific bugs, input differences, certification requirements, and performance constraints mean a test that passes on PC can fail catastrophically on mobile. This guide
Testing
Testing WearOS apps is different from phone testing. The screen is tiny, the interaction model is rotary input + swipe, and users expect extremely fast interactions — anything that takes more than 300ms feels slow on a watch. Horologist is Google's library for building and testing WearOS apps correctly. WearOS
Testing
Kaspresso is an Android UI test framework built on top of Espresso and UIAutomator. It solves the two biggest problems with raw Espresso: flaky tests and unreadable test code. With Kaspresso, you get a clean Kotlin DSL (via Kakao), automatic waiting and retry logic, and first-class Allure report integration.
Maestro
Maestro is a mobile testing framework that replaces imperative test code with declarative YAML flows. You describe what the user does — tap this, type that, assert visible — and Maestro handles synchronization, retries, and cross-platform execution. This guide covers the flow syntax, handling dynamic content, CI integration, and how Maestro
Test Automation
NativeWind v4 brings Tailwind CSS utility classes to React Native using a compiler that converts className strings into StyleSheet-compatible styles. Testing NativeWind components requires understanding what the compiler produces and how to assert it. This guide covers NativeWind v4 testing: className-based assertions, dark mode switching, responsive breakpoints, and
Test Automation
React Native's New Architecture — Fabric renderer, JSI (JavaScript Interface), and TurboModules — changes how native modules communicate with JavaScript. For testing, the key impact is that TurboModules use synchronous JSI calls instead of asynchronous bridge messages, and Fabric renders components differently from the legacy renderer. This guide covers testing
Test Automation
Maestro is a mobile E2E testing framework that drives your app through real gestures on a simulator or device. For Expo Router apps, Maestro tests the full navigation stack — deep links, tab switching, modal presentation, auth redirects — without needing to instrument your app code. This guide covers E2E testing Expo