# ui-testing UI testing is the practice of automating interactions with an application's user interface and checking its resulting behavior and state. 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 ## Android Journey Tests with Gemini: CI Setup & 11-Week Review DevFeed: [Android Journey Tests with Gemini: CI Setup & 11-Week Review]() Original publisher: [Read original article]() Author: Swapnil Gupta Published: 2026-06-19T03:27:13Z Content type: opinion Language: en Sources: [REA Group]() Topics: [Android](), [Artificial Intelligence](), [ui-testing](), [CI/CD](), [Android Studio](), [adb]() Tags: [adb](), [android](), [android-studio](), [ci](), [firebase](), [gemini](), [qa-engineer](), [quality](), [tech](), [tests]() ### AI overview An 11-week experiment evaluated Android Journeys powered by Gemini for AI-driven UI testing in REA Group's production Android app and CI infrastructure. The tests generally remained resilient through UI changes, but CI setup took eight weeks, Firebase Test Lab was unsupported, and manual QA hours did not decrease. The team rated the experience 8.75 out of 10 and voted to continue. ### Source excerpt Writing AI-powered UI tests took minutes. Getting them on CI took eight weeks. Here's what we learned after 11 weeks with Android Journeys and Gemini. ## 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. ## 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. ## 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 [...] ## 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. ## 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. ## 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. ## 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... ## UI tests with Jetpack Compose and Appium x UIAutomator DevFeed: [UI tests with Jetpack Compose and Appium x UIAutomator]() Original publisher: [Read original article]() Author: Julien Salvi Published: 2022-12-05T13:01:16Z Content type: tutorial Language: en Sources: [Stories by Julien Salvi on Medium]() Topics: [ui-testing](), [Jetpack Compose](), [Android](), [Testing](), [Instrumentation]() Tags: [android](), [appium](), [compose](), [instrumentation](), [jetpack-compose](), [testing](), [tests](), [ui-testing](), [uiautomator]() ### AI overview This tutorial explains how Aircall adapted Android UI automation tests when migrating from View-based components to Jetpack Compose. It describes using Compose semantics and testTag values mapped to resource IDs, then locating the resulting components with UiSelector in Appium and UIAutomator. ### Source excerpt At Aircall we are pushing a lot around quality thanks to our great QA team. Huge efforts are put on Android developer side with the unit tests and our QA engineers tackle everything around automation & UI tests. Before integrating our brand new design system made with Compose UI in production, we wanted to be sure that the transition to Compose would be painless with our automation framework and tools: Appium and UIAutomator. This article will explain how the Android team validated the move to Compose with our automation framework. Automation tests with View components The Aircall QA team has developed lots of automation tests that cover more than 90% of the use cases in the Android app. And to do so, they rely on Appium with the UI testing framework UIAutomator which is an instrumentation-based API and works with the AndroidJUnitRunner test runner. To locate a View-based component in the application, UIAutomator provides an annotation @AndroidFindBy where you need to specify the resource id of a UI element you want to identify. @AndroidFindBy(id = "myButtonId") protected WebElement myButton; But this method does work properly with Compose UI components. Indeed, when looking for a Composable with its dedicated tag, no elements are found in the screen. Now, let's have a closer look at the changes we had to make in order to smoothly add our new Compose code in the current codebase and not breaking everything on the automation side. UI tests with Compose UI and UIAutomator To unlock the UI testing with UIAutomator and Compose, we will have to take advantage of the semantics Modifier in each Composable we want to locate with the testTag property. In order to ease the migration, we are going to keep the same component IDs we were using with our View-based elements. Modifier.semantics { testTag = "myButtonId" } And at the top level Composable, we should toggle the configuration to map testTags to the resource IDs in the semantics Modifier. This will allow the automation f ## Writing Paparazzi tests for your Kotlin Multiplatform projects DevFeed: [Writing Paparazzi tests for your Kotlin Multiplatform projects]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2022-06-26T06:30:00Z Content type: tutorial Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Kotlin Multiplatform](), [Testing](), [Gradle](), [Kotlin](), [ui-testing](), [Compose](), [Android Library]() Tags: [android](), [android-library](), [compose](), [gradle](), [jetpack-compose](), [kotlin](), [kotlin-multiplatform](), [testing](), [ui-testing]() ### AI overview A tutorial on working around Paparazzi's lack of direct Kotlin Multiplatform support by placing Paparazzi tests in a separate Android library Gradle module. The approach enables JVM-based UI tests for public Compose composables, with additional guidance for CI build types, JDK 12+ compatibility, and testing multiple themes. ### Source excerpt Paparazzi enables a radically faster and improved UI testing workflow, and using a small workaround we can bring that to our multiplatform Compose projects ## Android UI screenshot testing across locales, font sizes, orientations, and UI modes DevFeed: [Android UI screenshot testing across locales, font sizes, orientations, and UI modes]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2022-03-30T05:29:19Z Content type: tutorial Language: en Sources: [Sergio's little tech corner]() Topics: [Android](), [screenshot-testing](), [ui-testing](), [ui](), [Testing](), [User experience (UX)]() Tags: [android](), [android-app-development](), [arabic](), [best-practices](), [design](), [language](), [layout](), [pixel](), [screenshot-testing](), [test](), [testing](), [ui-testing](), [ux]() ### AI overview This tutorial explains how Android screenshot testing can verify UI correctness across configurations such as locales, font sizes, orientations, and light or dark modes. It also discusses localization concerns including right-to-left layouts, mirrored drawables, and numeral systems. ### Source excerpt The success of your app depends heavily on its UI/UX. The more popular your app becomes, the more you should care about the diversity of your users. They might speak different languages, suffer from some sort of visual impairment, or feel too much ey... ## UI tests vs. snapshot tests on Android: which one should I write? 🤔 DevFeed: [UI tests vs. snapshot tests on Android: which one should I write? 🤔]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2021-12-15T21:03:56Z Content type: tutorial Language: en Sources: [Sergio's little tech corner]() Topics: [screenshot-testing](), [Testing](), [ui-testing](), [Android]() Tags: [android](), [android-app-development](), [best-practices](), [kotlin](), [screenshot-testing](), [testing](), [tests](), [ui-testing]() ### AI overview This Android testing article explains that UI tests and snapshot tests serve different purposes and should not replace each other. UI tests verify behavior and outcomes after interaction, while snapshot tests verify visual appearance across states and configurations such as themes, languages, font sizes, and screen widths. ### Source excerpt Snapshot tests on Android have become very popular lately. They run much faster and are easier to write than UI tests if done correctly. For those who've already fought with UI tests and are new to snapshot testing, it's normal to wonder why to still... ## A View-by-View Strategy for Snapshot Testing on Android DevFeed: [A View-by-View Strategy for Snapshot Testing on Android]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2021-09-23T20:22:08Z Content type: tutorial Language: en Sources: [Sergio's little tech corner]() Topics: [Testing](), [Android](), [ui-testing](), [ui]() Tags: [android](), [android-app-development](), [best-practices](), [how-to](), [introduction](), [recyclerview](), [testing](), [tests](), [ui](), [ui-testing]() ### AI overview This tutorial presents a view-by-view strategy for snapshot testing Android UI components. It explains why testing individual views can reduce synchronization work, simplify screen-state selection, and make flaky tests easier to diagnose, using a RecyclerView as an example. ### Source excerpt When one gets started with snapshot testing, there are not enough resources to learn from. It's no surprise to end up with snapshot tests causing a lot of headaches rather than helping improve the quality of our app. One should not snapshot test with... ## Android Library UI Tests & Firebase Test Lab DevFeed: [Android Library UI Tests & Firebase Test Lab]() Original publisher: [Read original article]() Author: JD Porterfield (jd.porterfield@alumni.rice.edu) Published: 2021-09-06T00:00:00Z Content type: tutorial Language: en Sources: [JD Porterfield | Articles]() Topics: [Firebase](), [Android Library](), [Testing](), [ui-testing]() Tags: [android](), [android-library](), [apk](), [ci-cd](), [command-line](), [firebase](), [test-lab](), [testing](), [ui]() ### AI overview This tutorial explains how to run Android library module UI tests with Firebase Test Lab. Because Test Lab requires separate test and application APKs with different package names, it presents a method for building the androidTest APK twice with different package names. ### Source excerpt Firebase Test Lab generally requires 2 .apk files for testing, how can we test library module UI tests in Test Lab? ## An introduction to snapshot testing on Android in 2021 📸 DevFeed: [An introduction to snapshot testing on Android in 2021 📸]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2021-08-09T20:07:20Z Content type: tutorial Language: en Sources: [Sergio's little tech corner]() Topics: [screenshot-testing](), [Android](), [Testing](), [ui-testing]() Tags: [android](), [android-app-development](), [best-practices](), [espresso](), [introduction](), [screenshot-testing](), [testing](), [ui](), [ui-testing](), [uiautomator]() ### AI overview This introduction explains snapshot testing on Android, also known as screenshot testing. It describes how snapshot tests compare rendered views with stored reference images, how they complement interaction-focused UI tests, and how they can detect visual regressions across commits. ### Source excerpt Snapshot testing (also called screenshot testing) has been in the Android world for a while, since 8th October 2015, when Facebook open sourced the first version of their snapshot testing library. They are a special type of UI tests that inflate a vi... ## Lessons Learned from Removing Android UI Tests from the CI Pipeline DevFeed: [Lessons Learned from Removing Android UI Tests from the CI Pipeline]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2018-05-26T00:00:00Z Content type: article Language: en Sources: [Artur Dryomov]() Topics: [Testing](), [ui-testing](), [Automation](), [Android](), [ci]() Tags: [android](), [automation](), [ci](), [testing](), [ui-testing]() ### AI overview This article shares lessons learned from removing Android UI tests from a continuous integration pipeline. It discusses the testing pyramid, the maintenance cost and flakiness of UI tests, and the role of unit tests and abstractions in creating maintainable tests. ### Source excerpt Automation is a foundation stone of the software development. People didn't like counting numbers themselves, so they invented calculators. Calculators went to be computers and here we go, waiting for AI to take over, watching movies about transhumanism on our way here. Automation related to UI testing seems to be a Holy Grail from that standpoint. Sure thing, it can replace manual QA procedures with automated ones! Like, completely! You just need to have a local backend... And maybe disable animations. And... you know, somehow wait for backend responses. And don't forget about the infrastructure. ## Painless UI Testing DevFeed: [Painless UI Testing]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2015-08-28T00:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [ui](), [ui-testing](), [Testing](), [Framework]() Tags: [framework](), [patterns](), [state](), [testing](), [ui](), [ui-testing](), [view]() ### AI overview This talk discusses practical ways to make UI tests faster and less burdensome. It covers deciding which parts of a UI need testing and using patterns such as supervising controllers, presenters, and view model state. ### Source excerpt What if you could get your UI tests to run as fast as your unit tests? you would write more tests you would feel happy writing the tests your managers would be pleased with you not goofing around with that new testing framework around the corner Using patterns of yore (like Martin Fowler's supervising controller, effective use of presenters and view model state) we're going to tackle everyday-real-annoying impediments to UI testing. We'll address what parts of the UI need testing and effective ways of testing them. The objective of the talk is to prove to the world that the title of this talk is not an oxymoron. Slides ##