# mobile-test-automation Published articles for mobile-test-automation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Presentation on Building React Native Test Automation with Detox and TypeScript DevFeed: [Presentation on Building React Native Test Automation with Detox and TypeScript]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-06-30T00:51:55Z Content type: article Language: en Sources: [T.J. Maher]() Topics: [Mobile Testing](), [React](), [TypeScript](), [CI/CD](), [Mobile](), [GitHub Actions](), [Vibe coding]() Tags: [ci-cd](), [github-action](), [mobile](), [mobile-test-automation](), [mobile-testing](), [react-native](), [testing](), [typescript](), [vibe-coding]() ### AI overview The article promotes T.J. Maher's presentation for the Sydney Testers Meetup on building automated tests for React Native applications with Wix's open-source Detox framework and TypeScript. ### Source excerpt If I presentation to the Sydney Testers Meetup in Australia, from my home in the Massachusetts, through Zoom, does that make me an international speaker? [ Vote in the New Poll, on LinkedIn ] There is still time to sign up for the event at: https://www.meetup.com/sydney-testers/events/315166776 "T.J. Maher, the former organiser at Ministry of Testing Boston, blogger and speaker, will be presenting from the US on using the Detox framework to create effective test automation frameworks for React Native applications. "Building a React Mobile Automated Test Framework using Detox + TypeScript by T.J. Maher "Writing automated tests for a React Native mobile application is notoriously difficult. Mobile components display on the page, but are not fully loaded. Lengthy animations and slow-loading components take a while to finish. Timing issues cause your automated tests to error out giving the appearance of flaky tests. "T.J. Maher will be sharing his experience tackling these problems using the open-source mobile testing framework, Wix's Detox, designed specifically for testing React Native applications. * "Setting up a mobile test automation framework. * "Vibe-coding a toy React Mobile Login page app to test against ( tinyurl.com/detox-demo ). * "How to reduce timing issues and flakiness in automated tests. * "Refactoring code into tests, page objects & base pages, separating out credentials and message strings for easier maintainability. * "Setting up automated tests in CI / CD for iOS simulators and Android emulators with GitHub Action Workflows. * "How developers can test their code before they push it into the main branch. "About T. J. Maher: --------------------- "A former organizer of the now defunct Ministry of Testing - Boston, T.J. Maher is a Senior Software Development Engineer in Test (SDET), based in the Boston/South Shore area of Massachusetts, with a decade of experience building web + mobile test automation frameworks. His recent work includes architecting ## Maestro's Architecture for Simplifying Mobile Test Automation DevFeed: [Maestro's Architecture for Simplifying Mobile Test Automation]() Original publisher: [Read original article]() Author: Leland Takamine Published: 2025-09-25T00:00:00Z Content type: article Language: en Sources: [mobile.dev - Medium]() Topics: [Mobile](), [Testing](), [Test automation](), [YAML](), [Accessibility](), [Open Source](), [Command-line interface](), [Android]() Tags: [accessibility](), [adb](), [android](), [flutter](), [ionic](), [maestro](), [mobile](), [mobile-test-automation](), [open-source](), [react-native](), [test-automation](), [yaml]() ### AI overview The article explains Maestro's architecture for mobile test automation. It describes one-line installation without separate dependencies, drivers, or SDKs; a Kotlin implementation of the ADB protocol called dadb; self-installing mobile drivers; and support for native, React Native, Flutter, and Ionic applications through the device accessibility layer. ### Source excerpt Discover how Maestro is revolutionizing mobile test automation with zero setup, universal compatibility, and human-readable YAML syntax. ## How to Input Unicode Characters in Maestro Android Tests: A Complete Workaround Guide DevFeed: [How to Input Unicode Characters in Maestro Android Tests: A Complete Workaround Guide]() Original publisher: [Read original article]() Author: Ishan Khanna Published: 2025-07-11T00:17:46Z Content type: tutorial Language: en Sources: [Ishan Khanna]() Topics: [Android](), [adb](), [HTTP](), [Flask]() Tags: [adb](), [android](), [automation](), [guide](), [javascript](), [maestro](), [mobile-test-automation](), [open-source](), [ui-testing]() ### AI overview A tutorial describing a workaround for Unicode text input in Maestro Android tests. It uses Maestro JavaScript, a local HTTP server, and ADB Keyboard to send Unicode text through Android broadcast intents. ### Source excerpt Learn how to overcome Maestro's Unicode input limitations on Android by building a custom HTTP server solution with ADB Keyboard. Complete implementation guide with code examples. ## Wahed Accelerates React Native Mobile Testing with Maestro DevFeed: [Wahed Accelerates React Native Mobile Testing with Maestro]() Original publisher: [Read original article]() Author: Jake Krupski Published: 2025-05-28T10:24:00Z Content type: article Language: en Sources: [mobile.dev - Medium]() Topics: [Mobile Testing](), [Test automation](), [React Native](), [Testing](), [Open Source]() Tags: [appium](), [case-study](), [fintech](), [maestro](), [mobile-test-automation](), [mobile-testing](), [react-native]() ### AI overview This case study describes how Wahed adopted Maestro for automated testing of its React Native mobile app. Test writing time fell from 3-4 hours per test with Appium to 10-15 minutes, releases shifted from biweekly to weekly, and automated test coverage grew from 50 manual smoke tests to approximately 250 tests. ### Source excerpt The world of mobile app development is fast-paced, demanding rapid iterations and flawless user experiences. But what happens when your mobile app testing process cannot keep up... ## Our Android testing process DevFeed: [Our Android testing process]() Original publisher: [Read original article]() Author: Headspace Published: 2022-06-22T05:16:52Z Content type: article Language: en Sources: [Stories by Headspace on Medium]() Topics: [Testing](), [Android](), [unit test](), [Mocking]() Tags: [android](), [android-testing](), [firebase](), [junit](), [mental-health](), [mobile-app-development](), [mobile-test-automation](), [mocking](), [quality-assurance](), [test-lab](), [testing]() ### AI overview Headspace describes its Android testing strategy after rewriting its app, including unit-test coverage standards, selective end-to-end testing, mocking, dependency injection, Robolectric, and Firebase Test Lab. ### Source excerpt Our testing strategy, how we integrate it into our development workflow, and what the future holds for testing at Headspace. By John Qualls, Senior Software Engineer, Greg Rami, Principal Software Engineer, and Anton Gerasimenko, Software Engineer Introduction When we took on the daunting task of rewriting our entire app at the end of 2019, one of our key focus areas was testability. At the time, we had less than 20% of our code covered by unit tests -- no integration or end-to-end (E2E) tests -- and adding any tests to the code base was a big effort. From the beginning, we agreed on the standard of at least 80% unit test coverage on all Pull Requests (PRs), E2E tests for critical flows, and an architecture that was focused on testability. The result is a more robust codebase. Today, we're able to capture critical bugs via our tests suite coverage before they hit our users and, very importantly, it's now trivial, and very fast, to add new tests. Let's detail our testing strategy, how we integrate it into our development workflow, and what the future holds for testing at Headspace. Testing Strategy Shortly after the rewrite, we had hundreds of unit tests and around twenty E2E tests. We wanted to optimize the number of E2E tests that we do to only certain use cases where it makes sense to take on the additional time and costs in exchange for the reduced risk. Test selection pyramid for cost and speedUnit Tests Our unit tests are straightforward. They test a very small unit of code by relying on JUnit 5 and different layers of mocking: MockK to mock all the dependencies that are unrelated to the current test. This is made easier by using good architecture principles such as Single Responsibility Principle (SRP) and Dependency Injection (DI) We introduced a Java Faker library, that provides "fakes" for primitive values that do not need to have a specific value Similarly, we have our own "model Fakers" that provide domain objects. That way when the underlying classes chang