Test Automation
Expo Router brings file-based routing to React Native with full TypeScript support. Each file in your app/ directory maps to a route, layouts wrap segments, and tabs and modals are first-class patterns. Testing all of this requires understanding what Expo Router provides and what you need to verify
Test Automation
EAS Build creates native iOS and Android builds in the cloud. For testing, EAS provides three distinct opportunities: preview builds for QA teams, build-time validation of native plugins, and production-equivalent builds for E2E testing. This guide covers testing strategies across the EAS Build pipeline: structuring build profiles, validating
Testing
Maestro takes a different approach to mobile UI testing than most frameworks. Instead of writing JavaScript or Python test code, you define flows in YAML. Instead of requiring build-time instrumentation, it works with any app — debug builds, release builds, or even apps you don't have the source
Testing
Running mobile E2E tests locally is one thing. Getting them to run reliably in CI is another problem entirely. You're dealing with emulators that need time to boot, builds that need to be cached, iOS simulators that require macOS runners, and Android emulators that need KVM acceleration or
Testing
If you're building a React Native app and need E2E tests, you'll eventually choose between Detox and Maestro. They're the two most widely used options, they take fundamentally different architectural approaches, and the right choice depends heavily on your team's structure and
Mobile Testing
Capacitor native plugins are the points in your application where web code makes requests to native capabilities — camera hardware, the device filesystem, push notification infrastructure. In unit and integration tests, none of those native capabilities exist. The test runner is Node.js; there is no camera, no iOS sandbox, no
Mobile Testing
Capacitor bridges the gap between web and native mobile, but that bridge creates a testing challenge. Your business logic calls Camera.getPhoto() or Geolocation.getCurrentPosition(), but in a Jest environment there is no native runtime — those calls throw immediately. Meanwhile, your Cypress tests run in a browser where the Capacitor
Mobile Testing
End-to-end testing a Capacitor application is fundamentally different from testing a pure native app. Your app is a native shell containing a WebView. User interactions flow from native gesture recognizers into the WebView's JavaScript runtime and back out through the Capacitor plugin bridge. Both Detox and
Mobile Testing
Testing Ionic Angular applications requires navigating a collision between two opinionated frameworks, each with their own component lifecycle and dependency injection patterns. Angular's TestBed assumes synchronous or promise-based initialization; Ionic's components wrap Web Components and initialize asynchronously. Modal controllers, alert controllers, and navigation all introduce
Mobile Testing
A Capacitor app CI/CD pipeline has more moving pieces than a typical web application. The web layer needs a standard JavaScript build, but then Capacitor must sync that output to native iOS and Android projects, each of which needs its own build toolchain, signing configuration, and deployment target. Add
Testing
Compose Multiplatform extends Jetpack Compose beyond Android, bringing the same declarative UI model to iOS, desktop (macOS, Windows, Linux), and web. But testing a UI that runs on four platforms is a different challenge than testing a single-platform app. This guide covers how to write and run Compose Multiplatform
Testing
Kotlin Multiplatform (KMP) lets you write business logic once and share it across Android, iOS, desktop, and web. But sharing code means shared bugs — and shared testing responsibilities. This guide covers everything you need to test KMP projects effectively. Why Testing KMP Is Different In a typical Android project, your