# ui-testing Published articles for ui-testing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Automating App Store Screenshots DevFeed: [Automating App Store Screenshots]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-03-27T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [iOS](), [ui-testing](), [Xcode](), [Sketch](), [Mobile](), [Testing]() Tags: [app-store](), [design](), [engineering](), [fastlane](), [ios](), [iphone](), [mobile](), [news](), [screenshots](), [testing](), [ui-testing](), [xcode]() ### AI overview A tutorial describing how Khan Academy automated App Store and Play Store screenshots with Xcode UI tests, Fastlane, a Snapfile, and a homegrown Sketch file. The team reduced screenshot update time from about a week to about an hour. ### Source excerpt By Bryan Clark One of the more tedious design tasks is keeping your App Store promo images up-to-date. ... Read more ## Everything You Need to Know About Patrol in 2026 DevFeed: [Everything You Need to Know About Patrol in 2026]() Original publisher: [Read original article]() Author: LeanCode Published: 2026-07-24T02:52:52Z Content type: tutorial Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Mobile Testing](), [ui-testing](), [multiplatform](), [ci](), [Android](), [iOS](), [Web](), [Open Source]() Tags: [ai](), [android](), [automation-testing](), [ci](), [e2e-testing](), [flutter](), [flutter-app-development](), [ios](), [mobile](), [mobile-testing](), [multiplatform](), [open-source](), [ui-testing](), [web]() ### AI overview This article explains Patrol, an open-source multiplatform end-to-end UI testing framework for Flutter apps. It describes how Patrol combines Flutter testing APIs with native Android and iOS UI automation to test Flutter widgets alongside system dialogs, biometric prompts, notifications, and other native interfaces, while integrating with CI pipelines and device farms. ### Source excerpt Author: Katarzyna Szulc from LeanCode Patrol has come a long way from being "just another Flutter testing tool." Today, it powers end-to-end testing across Android, iOS, and Web, integrates with native testing infrastructure, runs on cloud device farms, offers AI-powered testing capabilities, and continues to push the boundaries of what's possible in the Flutter ecosystem. No matter if you've been following Patrol for a while or you're simply looking for the best way to handle Flutter E2E testing, this article is the perfect place to catch up. What exactly is Patrol? Let's break it down Developed by LeanCode, Patrol is a powerful, open-source, multiplatform E2E UI testing framework for Flutter apps that overcomes the limitations of integration_test by handling native interactions. Let's dig deeper into that. Flutter's greatest strength also creates one of its biggest testing challenges. Unlike native apps, Flutter renders its entire UI using its own graphics engine instead of platform-native components. This enables a consistent, pixel-perfect experience across devices, but it also means that native UI automation tools often see a Flutter app as little more than a single canvas. They simply cannot interact with Flutter widgets. The official solution is the integration_test package, which gives tests direct access to the Flutter widget tree. As long as everything happens inside Flutter, it works well. But real apps rarely stay there. System permission dialogs, biometric prompts, notifications, WebViews, and other native UI all exist outside the Flutter runtime, making them inaccessible to integration_test. Patrol bridges this gap. It lets tests interact with both Flutter widgets and native UI elements in a single test. Because Patrol builds on native frameworks such as JUnit and XCTest, it also integrates seamlessly with existing CI pipelines, device farms, and the broader mobile testing ecosystem. If you are new to automating E2E testing in Flutter, you can start by ## Verification Is the Next Bottleneck DevFeed: [Verification Is the Next Bottleneck]() Original publisher: [Read original article]() Author: Ishan Khanna Published: 2026-07-20T05:13:15Z Content type: opinion Language: en Sources: [Ishan Khanna]() Topics: [Testing](), [Artificial Intelligence](), [AI Agent](), [Code](), [Mobile]() Tags: [ai](), [ai-agent](), [android](), [code](), [ios](), [testing](), [ui-testing](), [verification]() ### AI overview The article argues that AI-generated code is increasing development output faster than teams can review and test it, making verification the next bottleneck. Drawing on conversations at Droidcon USA and work at DoorDash, it discusses efforts to automate mobile testing and the challenge of making AI-driven verification fast and deterministic. ### Source excerpt Engineers spent decades treating testing as someone else's job. Now AI generates code faster than anyone can review it, and verification has become the bottleneck. Notes from Droidcon hallway conversations, and what I'm building at DoorDash to fix it. ## Writing interactive screenshot tests in Compose UI with Touch Robot DevFeed: [Writing interactive screenshot tests in Compose UI with Touch Robot]() Original publisher: [Read original article]() Author: Saket Narayan Published: 2026-05-24T06:09:55Z Content type: tutorial Language: en Sources: [Saket Narayan]() Topics: [Compose](), [screenshot-testing](), [ui-testing](), [Testing]() Tags: [android](), [compose](), [screenshot-testing](), [snapshots](), [testing](), [ui-testing]() ### AI overview The article explains how Block built Touch Robot to generate fake touch events for interactive screenshot tests in Compose UI. It describes using animated PNG snapshots to verify interactions such as clicks, swipes, drawing, and pinch gestures, with deterministic frame comparisons for regression testing. ### Source excerpt These are some examples of real issues that were happening at Block. Each of them was frustrating because we were regularly shipping broken experiences to customers despite having sufficient test coverage. We had screenshot tests using Paparazzi, but they were mostly static snapshots that verified layout correctness. We had connected device tests, but they ran [...] The post Writing interactive screenshot tests in Compose UI with Touch Robot appeared first on Saket Narayan. ## New Maestro Studio DevFeed: [New Maestro Studio]() Original publisher: [Read original article]() Author: Manu Armani Published: 2026-04-21T22:36:00Z Content type: release Language: en Sources: [mobile.dev - Medium]() Topics: [Mobile](), [Testing](), [Tool](), [selectors](), [Emulator]() Tags: [amazon](), [autocomplete](), [cli](), [developers](), [emulator](), [maestro](), [meta](), [testing](), [ui-testing]() ### AI overview Maestro announces a redesigned Maestro Studio desktop app for mobile UI testing. The release adds contextual autocomplete for commands, arguments, and selectors, emulator-assisted test creation, and more robust device connections, while existing tests continue to work without migration. ### Source excerpt Maestro Studio is the desktop app for mobile UI testing. Now completely redesigned, with contextual autocomplete. ## Migrating 76,000 Tests from Enzyme to React Testing Library DevFeed: [Migrating 76,000 Tests from Enzyme to React Testing Library]() Original publisher: [Read original article]() Author: Charley Pugmire Published: 2025-11-13T18:31:47Z Content type: tutorial Language: en Sources: [HubSpot]() Topics: [testing-library](), [React](), [Testing](), [migration](), [ui-testing]() Tags: [engineering](), [migration](), [react](), [testing](), [testing-library](), [ui-testing]() ### AI overview The article explains how a team migrated more than 76,000 tests from Enzyme to React Testing Library over two and a half years. It describes the shift toward user-focused UI tests, the planning process, and the limits of using static analysis alone to estimate the work. ### Source excerpt For years, Enzyme was the de facto standard for testing React applications. Originally built by Airbnb in 2015, Enzyme makes it easy to assert, manipulate, and traverse the output of React components. The last official release of Enzyme came after React 16 was launched in 2017, but even then did not fully support all React 16 features. Ongoing support for Enzyme shifted to the open source community with React 17. However, the creator of the community-maintained Enzyme adapter announced that he would not be offering an updated version for React 18. This effectively marked the end of the Enzyme project, as it would prevent users from leveraging new features like React 18's concurrent mode. ## 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. ## Google Maps UI Test Automation with Maestro - Full Tutorial DevFeed: [Google Maps UI Test Automation with Maestro - Full Tutorial]() Original publisher: [Read original article]() Author: Leland Takamine Published: 2025-07-01T16:23:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [Test automation](), [Google Maps](), [Automation](), [YAML](), [Tutorial](), [Mobile]() Tags: [automation](), [cli](), [google-maps](), [maestro](), [maps](), [open-source](), [test-automation](), [tutorial](), [ui-testing](), [yaml]() ### AI overview A step-by-step tutorial for automating a Google Maps UI test with the open-source Maestro framework. It covers installing the Maestro CLI, launching the app with clearState, tapping, typing, swiping, scrolling until an element is visible, validating with regex, and running a complete YAML flow. ### Source excerpt Discover step-by-step automated Google Maps UI testing with Maestro: complete YAML guide to tap, input, swipe, scroll commands and fast assertions. ## Using Compose Previews to Preview XML-Based Android Views DevFeed: [Using Compose Previews to Preview XML-Based Android Views]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2024-12-17T20:09:09Z Content type: tutorial Language: en Sources: [Sergio's little tech corner]() Topics: [Jetpack Compose](), [XML](), [Android](), [ui](), [Code]() Tags: [android](), [android-app-development](), [android-studio](), [compose](), [jetpack-compose](), [layout](), [recyclerview](), [testing](), [ui](), [ui-testing](), [xml]() ### AI overview This tutorial explains how Jetpack Compose Previews can be used to preview XML-based Android Views, including ViewHolder UI logic and dynamic behavior that static XML previews cannot represent. ### Source excerpt Jetpack Compose has transformed Android UI development with its declarative approach, making UI code simpler to write. One of its standout features is Compose Previews, which allows developers to instantly view how Composable functions will look on a... ## UI Testing Made Easy: The Robot Test Pattern on Android DevFeed: [UI Testing Made Easy: The Robot Test Pattern on Android]() Original publisher: [Read original article]() Author: Michael Evans Published: 2024-12-14T15:52:24Z Content type: article Language: en Sources: [Gadget Habit]() Topics: [Testing](), [Android](), [ui](), [Compose](), [Code]() Tags: [android](), [android-testing](), [best-practices](), [compose](), [jetpack-compose](), [patterns](), [testing](), [ui](), [ui-testing]() ### AI overview This guide explains the Robot Testing Pattern for Android UI testing. It describes how robots abstract UI interactions from test logic, improving readability, maintainability, reuse, organization, parallel execution, and stability. It also covers implementations for Jetpack Compose and traditional View-based applications, along with base robots and recommended practices. ### Source excerpt As Android applications grow in complexity, maintaining a robust testing strategy becomes increasingly challenging. The "Robot Testing Pattern" offers a structured approach to UI testing that can significantly improve your test suite's maintainability and reliability. This guide is designed for Android developers who have basic experience with testing and want to enhance their testing methodology. Understanding the Robot Pattern The Robot Testing Pattern, also known as the Robot Framework or Robot Pattern, is a testing methodology that creates an abstraction layer between your test code and UI interactions. Think of robots as specialized assistants that handle all the UI interactions on behalf of your tests. Key Benefits The Robot Pattern provides several advantages that make it particularly valuable for Android testing: Improved Test Readability: Tests become high-level descriptions of user behavior rather than low-level UI interactions, making them easier to understand and maintain. Enhanced Maintainability: When UI changes occur, updates are needed only in the robot implementation rather than across multiple test files. Code Reusability: Common interactions can be shared across multiple test cases, reducing duplication and ensuring consistency. Better Test Organization: The pattern enforces a clear separation between test logic and UI interaction code. Simplified Parallel Testing: Isolated UI interaction logic enables efficient parallel test execution and better test stability. Implementation Guide Let's explore how to implement the Robot Pattern in both Jetpack Compose and traditional View-based applications. Jetpack Compose Implementation Here's a basic implementation for a login screen using Compose: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 class LoginRobot { private val composeTestRule = createComposeRule() fun enterUsername(username: String) = apply { composeTestRule.onNodeWithContentDescription("UsernameTextField") .performTextInput(us ## LLM Based Android UI Testing - "Journeys with Gemini" DevFeed: [LLM Based Android UI Testing - "Journeys with Gemini"]() Original publisher: [Read original article]() Author: Sam Edwards Published: 2024-12-09T15:17:57Z Content type: article Language: en Sources: [Handstand Sam]() Topics: [ui-testing](), [Testing](), [Android](), [Large Language Model](), [Android Studio](), [Google](), [Gradle]() Tags: [2025](), [ai](), [android](), [android-studio](), [aosp](), [gemini](), [google](), [gradle](), [llm](), [model](), [testing](), [ui](), [ui-testing](), [updates]() ### AI overview The article examines the proposed "Journeys with Gemini" feature for Android UI testing. Based on public previews, it describes human-readable test steps stored in .journey.xml files, IDE-based tooling, and placeholder AOSP components, while presenting availability and connectivity details as predictions. ### Source excerpt What Do We Know About "Journeys With Gemini"? "Journeys with Gemini" was first (to my knowledge) discussed publicly at Droidcon London during a segment of #TheAndroidShow by Tor Norbye of the Android Studio team. We saw a sneak peek of a new way to write UI tests for Android using Google's Gemini (AI Model) that [...] ## The Ultimate Guide to Developing High-Quality Android Libraries DevFeed: [The Ultimate Guide to Developing High-Quality Android Libraries]() Original publisher: [Read original article]() Author: Akshay Bora Published: 2024-12-04T08:27:06Z Content type: tutorial Language: en Sources: [Android@Microsoft - Medium]() Topics: [Android Library](), [Library](), [Development](), [API](), [Testing](), [Developer experience]() Tags: [android](), [api](), [build-times](), [consistency](), [documentation](), [error-handling](), [guide](), [libraries](), [library-design](), [mobile](), [quality](), [ui-testing]() ### AI overview A practical guide to developing high-quality Android libraries. It recommends using a dedicated playground or development app for isolated feature development, shorter build times, UI testing, easier replacement of implementations, and better integration references. It also advises maintaining a simple, consistent, well-documented, encapsulated API with graceful error handling. ### Source excerpt In the fast-paced world of software development, creating Libraries efficiently and effectively is crucial to ensure the code reuse across apps. Here are some preferred practices to help you streamline your Library development process and guide you towards unlocking the secrets of building a top-notch Android Library. In Microsoft we do use these guidelines while developing the Libraries like File Picker, Share and Calendar libraries which helped us big time. 1. Create a Playground/Development App When developing libraries, it is advantageous to create a playground or development application that integrates with the library for faster development cycles. This approach has proven highly beneficial, as developers no longer need to build an example Teams codebase to test the libraries, significantly reducing the time required for testing. This approach offers several benefits: Isolated Testing: Developers can test and develop features in isolation, without waiting for integration into the consumer codebase. This leads to faster development cycles. Shorter Build Times: The development app targets specific features, resulting in quicker builds. Developers can launch the feature they want to test with just a click. UI Testing: Run UI tests from the playground app, allowing the consumer or library to focus on integration tests. Feature-level UI tests can be handled in isolation. Easier Replacement: Replace actual implementations with fake ones for UI tests easily. Better Integration References: Provide better integration references in developer documentation and stakeholders to play around before consuming the Library. 2. Cleaner API Surface When developing high-quality Android libraries, it's crucial to maintain a clean and intuitive API surface. A cleaner API surface ensures that your library is easy to understand and use, which can significantly enhance the developer experience. Simplicity: Keep your API simple and avoid unnecessary complexity. Provide clear, concise me ## Demystifying Maestro's UI Testing Implementation DevFeed: [Demystifying Maestro's UI Testing Implementation]() Original publisher: [Read original article]() Author: Sam Edwards Published: 2024-11-18T13:59:04Z Content type: article Language: en Sources: [Handstand Sam]() Topics: [Testing](), [ui-testing](), [Android](), [Code](), [Git]() Tags: [adb](), [android](), [android-testing](), [code](), [format](), [git](), [library](), [maestro](), [on-device](), [open-source](), [server](), [testing](), [ui](), [ui-testing](), [uiautomator](), [updates](), [xml]() ### AI overview This technical post examines how Maestro implements UI testing. It describes its YAML-based test commands, CLI-installed APKs, an on-device Netty gRPC server, UiAutomator view-hierarchy access, XML serialization, and UI interactions. ### Source excerpt I first heard about Maestro when it was released in 2022, but I haven't played with it until now. I'm doing some work with Espresso and UiAutomator for Android testing and was curious how Maestro worked under the hood, so I cloned their git repo and dove into the code. This quick post shares what [...] ## Implementing Radial Swipes in UI Tests DevFeed: [Implementing Radial Swipes in UI Tests]() Original publisher: [Read original article]() Author: Amanjeet Singh Gurtatta Published: 2024-02-20T12:36:00Z Content type: tutorial Language: en Sources: [Amanjeet Singh]() Topics: [Testing](), [ui-testing](), [JavaScript](), [Android](), [math]() Tags: [android](), [automation](), [javascript](), [maestro](), [math](), [testing](), [tests](), [ui](), [ui-testing](), [uitest]() ### AI overview A tutorial on implementing radial swipe gestures for UI tests. It derives points along a circular arc with parametric equations and uses JavaScript and Maestro to generate swipe coordinates for an Android clock alarm test. ### Source excerpt Discover the intricacies of implementing a radial swipe in UI testing with a step-by-step guide. We'll unravel how to tackle this with an example of Android clock app. ## Mastering UI Testing for Android web forms DevFeed: [Mastering UI Testing for Android web forms]() Original publisher: [Read original article]() Author: Vaios Tsitsonis Published: 2024-01-05T11:50:19Z Content type: tutorial Language: en Sources: [Blueground Engineering blog]() Topics: [Android](), [Testing](), [WebView](), [Forms](), [JavaScript](), [HTML]() Tags: [android](), [forms](), [html-elements](), [javascript](), [testing](), [ui-testing](), [web](), [webview]() ### AI overview This tutorial explains a UI-testing problem in Android apps that open web forms in a WebView. Programmatically changing HTML input values can mark related JavaScript events as non-trusted, leaving a button disabled even when the fields display values. ### Source excerpt Yeah! We are Android engineers! 🎉 We can build almost anything by ourselves and make it run on any Android device! But sometimes we may need to use a third-party library or incorporate web-based functionality into a WebView to go fast. This can introduce challenges during UI testing. ## Review of 2023 DevFeed: [Review of 2023]() Original publisher: [Read original article]() Author: Alex Zhukovich Published: 2024-01-04T19:36:53Z Content type: opinion Language: en Sources: [Alex Zhuk - Android development and testing]() Topics: [Mobile](), [android-development](), [Testing](), [ui](), [Jetpack Compose]() Tags: [android](), [android-development](), [annual-review](), [development](), [jetpack-compose](), [mobile-development](), [review](), [speaking](), [testing](), [ui-testing]() ### AI overview A personal review of 2023 covering mental-health routines, blog publishing, Android development and testing tips, public speaking about UI testing, and goals for 2024. ### Source excerpt Review of 2023 The first week of 2024 is an excellent opportunity to reflect on the previous year and set goals for the upcoming one. The 2023 was pretty challenging for me in multiple areas of my life, like mental state and content creation. I'd like to share ## Types of UI Tests and What They Verify DevFeed: [Types of UI Tests and What They Verify]() Original publisher: [Read original article]() Author: Alex Zhukovich Published: 2023-11-17T00:11:25Z Content type: tutorial Language: en Sources: [Alex Zhuk - Android development and testing]() Topics: [ui](), [Testing](), [Accessibility](), [Development]() Tags: [accessibility-testing](), [android-testing](), [how-to](), [software-development](), [testing](), [tests](), [ui](), [ui-testing]() ### AI overview This tutorial explains several types of UI testing: end-to-end tests, UI tests with fake data, screenshot or pixel-perfection tests, and accessibility tests. It describes what each type can verify and introduces ways to begin UI testing in a project. ### Source excerpt The article explores different types of UI testing, such as end-to-end testing, UI testing with fake data, pixel perfection testing, and accessibility testing. The article also includes information on how to get started with UI testing in any project. ## Efficient Testing with Robolectric & Roborazzi Across Many UI States, Devices and Configurations DevFeed: [Efficient Testing with Robolectric & Roborazzi Across Many UI States, Devices and Configurations]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2023-11-09T21:45:00Z Content type: tutorial Language: en Sources: [Sergio's little tech corner]() Topics: [Testing](), [screenshot-testing](), [ui-testing](), [Android](), [Software Process](), [enum]() Tags: [android](), [android-app-development](), [devices](), [emulator](), [espresso](), [google](), [robolectric](), [roborazzi](), [screenshot-testing](), [screenshots](), [software](), [software-process](), [testing](), [tests](), [ui](), [ui-testing]() ### AI overview This tutorial explains how to use Robolectric and Roborazzi for screenshot testing across many UI states, devices, and configurations. It introduces parameterized tests, enum-based UI states, and device qualifiers for generating screenshots efficiently. ### Source excerpt Robolectric is a popular UI testing tool from Google that enables running UI tests without a physical device or emulator. It supports most androidx.test APIs, like Espresso, ActivityScenario & FragmentScenario as well as ComposeTestRule. Robolectric ... ## Screenshot Tests Are Manual Tests DevFeed: [Screenshot Tests Are Manual Tests]() Original publisher: [Read original article]() Published: 2023-10-17T16:00:00Z Content type: opinion Language: en Sources: [Blogs on Ryan Harter]() Topics: [screenshot-testing](), [Testing](), [ui-testing](), [test-coverage]() Tags: [code-coverage](), [screenshot-testing](), [testing](), [ui-testing]() ### AI overview The article explains that screenshot tests validate UI appearance and can reveal visual changes, but they do not validate application behavior. It argues that screenshot-based coverage can increase coverage numbers while still requiring manual review and complementary UI testing. ### Source excerpt When I joined Dropbox almost 2 years ago, I was asked to help improve the screenshot testing experience, resulting in Dropshots. While I'd played around with early versions of Paparazzi by that point, many of our tests were too heavily reliant on full Activities and Fragments to make use of host side JUnit tests. The more I've worked with screenshot tests, the more I've come to understand their promises and limitations. What screenshot tests offer Screenshot testing can be really helpful to validate that elements on the screen are rendered as you expect. They can help you detect visual changes that might have otherwise gone unnoticed. ## Music App UI Testing Series: End-to-End Flutter Testing with Maestro -- Part 2 DevFeed: [Music App UI Testing Series: End-to-End Flutter Testing with Maestro -- Part 2]() Original publisher: [Read original article]() Author: Ashish Kharche Published: 2023-10-17T07:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Flutter](), [Testing](), [App](), [Development]() Tags: [android](), [app](), [app-development](), [flutter](), [guide](), [ios](), [testing](), [ui-testing]() ### AI overview This tutorial explains how to write end-to-end UI tests for a Flutter music app using Maestro on Android and iOS. It covers workspace setup, flow execution order, and organizing tests into journeys and reusable subflows. ### Source excerpt Write UI tests for your Flutter Apps ## Music App UI Testing Series: Getting Started with Maestro in Flutter -- Part 1 DevFeed: [Music App UI Testing Series: Getting Started with Maestro in Flutter -- Part 1]() Original publisher: [Read original article]() Author: Ashish Kharche Published: 2023-10-05T07:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Flutter](), [Testing](), [ui](), [App](), [Visual Studio Code](), [Emulator](), [Android](), [iOS](), [browser]() Tags: [android](), [app](), [debugging](), [emulator](), [flutter](), [getting-started](), [gui](), [guide](), [how-to](), [ios](), [maestro](), [simulator](), [testing](), [ui](), [ui-testing](), [visual-studio-code](), [web-browser]() ### AI overview A step-by-step guide to configuring Flutter and using Maestro to perform UI testing on Android and iOS applications, demonstrated with the Blackhole Music app. ### Source excerpt Setup and Configure Flutter for Maestro UI Testing ## How To Ensure Exceptional Software Quality On Mobile DevFeed: [How To Ensure Exceptional Software Quality On Mobile]() Original publisher: [Read original article]() Author: Ben Published: 2023-09-26T08:49:48Z Content type: tutorial Language: en Sources: [Novoda]() Topics: [Mobile](), [Testing](), [Maintainability](), [ui-testing](), [Unit testing](), [Scalability]() Tags: [engineering](), [how-to](), [maintainability](), [mobile](), [mobile-development](), [mobile-devops](), [mobile-engineering](), [quality](), [testing](), [ui-testing](), [unit-testing]() ### AI overview This tutorial explains software quality for mobile products through the testing pyramid, performance and stability metrics, scalability, and maintainability. It emphasizes unit tests as a foundation, followed by integration and UI tests to validate component interactions and user flows. ### Source excerpt Explore the key ways to ensure exceptional software quality on mobile including the pyramid of testing, performance and stability metrics, scalability and maintainability. The post How To Ensure Exceptional Software Quality On Mobile appeared first on Novoda. ## Pokedex UI Testing Series: Taking Maestro to the Cloud with Expo EAS & GitHub Actions -- Part 3 DevFeed: [Pokedex UI Testing Series: Taking Maestro to the Cloud with Expo EAS & GitHub Actions -- Part 3]() Original publisher: [Read original article]() Author: Ashish Kharche Published: 2023-09-21T07:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Expo](), [Testing](), [GitHub Actions](), [Cloud](), [React Native](), [GitHub]() Tags: [android](), [cloud](), [github](), [github-actions](), [ios](), [maestro](), [react-native](), [testing](), [ui](), [ui-testing]() ### AI overview Part 3 of a series explains how to run Expo React Native UI tests with Maestro Cloud, Expo Application Services builds, and GitHub Actions. It covers managed iOS and Android environments, parallel runs, test artifacts, CI integration, and the workflow steps for building and testing the apps. ### Source excerpt Expo EAS / React Native UI testing on Maestro Cloud ## Write Once, Test Everywhere: Cross-Library Screenshot Testing with AndroidUiTestingUtils 2.0.0 DevFeed: [Write Once, Test Everywhere: Cross-Library Screenshot Testing with AndroidUiTestingUtils 2.0.0]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2023-09-15T15:06:04Z Content type: tutorial Language: en Sources: [Sergio's little tech corner]() Topics: [screenshot-testing](), [ui-testing](), [Testing](), [Android]() Tags: [android](), [android-app-development](), [robolectric](), [roborazzi](), [screenshot-testing](), [testing](), [ui-testing]() ### AI overview This tutorial explains how AndroidUiTestingUtils 2.0.0 supports cross-library screenshot tests. It describes a common interface for device configuration, the subject under test, and screenshot recording or verification, with separate modules for Paparazzi, Dropshots, Roborazzi, and Shot. It also discusses enabling Robolectric Native Graphics mode through Gradle. ### Source excerpt As observed in the previous blog post of this series, screenshot tests have a lot in common regardless of the library they're written with, namely: Setting the device configuration (e.g. Locale, Ui Mode, Font scale...) Setting the Subject Under Tes... [Next page]()