# Espresso Published articles for Espresso. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kaspresso: cравниваем скриншоты и упрощаем проверку дизайна DevFeed: [Kaspresso: cравниваем скриншоты и упрощаем проверку дизайна]() Original publisher: [Read original article]() Author: Nikita-e57 ("Лаборатория Касперского") Published: 2026-03-31T14:20:02Z Content type: tutorial Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [Android](), [ui](), [API]() Tags: [android](), [espresso](), [kaspresso](), [kotlin](), [tag-1623e2d0e12a](), [tag-20e69fa9a855](), [tag-831b63de9433](), [tag-909d03ed6dc5](), [tag-95d977179ee2](), [tag-c34eb7014865](), [tag-e932065bc8da](), [ui]() ### AI overview A Russian-language tutorial introduces Kaspresso's screenshot comparison feature for Android UI tests. It explains how to integrate Kaspresso, capture a baseline screenshot, compare later test runs, and handle storage permissions across Android API versions. ### Source excerpt Хабр, привет! Меня зовут Никита Евдокимов, я работаю старшим разработчиком в "Лаборатории Касперского", а также являюсь мейнтейнером репозитория Kaspresso. Это наш фреймворк для тестирования пользовательских интерфейсов на Android, основанный на Kakao, Espresso и UI Automator. Недавно в нем появилась новая функция: сравнение скриншотов. С ней можно записывать скриншоты приложения, а на последующих прогонах автотестов сравнивать их с новыми скриншотами и отслеживать изменения в интерфейсе. В статье я пошагово покажу, как с ней работать, со скриншотами и примерами кода. Материал подойдет для как опытных, так и начинающих специалистов в области автотестирования, а также для дизайнеров: функция облегчает автоматическое тестирование, с ней быстрее и проще проверять, соответствует ли разработанное приложение макету. Читать далее ## Deprecating idling resource libraries DevFeed: [Deprecating idling resource libraries]() Original publisher: [Read original article]() Published: 2025-02-19T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [Testing](), [Monitoring](), [Compose](), [ui]() Tags: [blog-post](), [compose](), [espresso](), [monitoring](), [testing](), [tests](), [ui]() ### AI overview The article announces the deprecation of the RxIdler and okhttp-idling-resource libraries. It argues that tests should wait for user-visible UI conditions rather than internal application mechanisms, and points to Compose testing APIs and custom condition-waiting approaches for View-based layouts. ### Source excerpt When Espresso was made public a decade ago, one of its banner features was the "idling resource" concept. This monitored the main thread and any background thread pools to prevent your test from progressing until the app became idle. Waiting until idle generally increased the stability of tests since at that point the UI should be stable. We released RxIdler and okhttp-idling-resource for monitoring RxJava schedulers and OkHttp's dispatcher, respectively. Today I am deprecating both libraries. In the years since their release, I have become disillusioned with the idling resource mechanism-and I'm not alone. Like using R.id to target views, idling resources expose the internals of your application to the testing framework in a way that no real user can match. The point of building tests in the robot pattern was to describe interaction at a high-level. If you can't read a UI test to someone over the phone interacting with the real app then it probably encodes implementation detail. "Okay dad, now wait for OkHttp's Dispatcher to report itself as idle before clicking 'continue'." Yeah... no. What do we do as real users? We wait until some UI condition is met which signals our ability to progress. "Okay dad, now wait for the 'continue' button to turn green before clicking it." Much better. We don't care how the application is performing the work nor the means by which it signals the UI that it is complete. Moreover, test failures that occur based on condition waits are failures which can occur in the wild. I've been sitting on these deprecations and this blog post for a few years now. Telling you to switch to a new technique without actually demonstrating it is not great. Turns out that around the same time Google was also changing their tune on idling resources. That guidance has since been promoted to the official documentation as well. These links demonstrate how to wait on conditions using new built-in Compose testing APIs. For View-based layouts, you can write a custo ## Espresso Machine PID controller using ESP32 and RainMaker DevFeed: [Espresso Machine PID controller using ESP32 and RainMaker]() Original publisher: [Read original article]() Author: John Lee Published: 2024-06-19T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Algorithm]() Tags: [blog](), [connectivity](), [cost](), [esp-idf](), [esp32](), [espresso](), [machine](), [rainmaker]() ### AI overview This article describes upgrading a low-cost espresso machine with an ESP32 for control and connectivity. It discusses coffee channeling, pre-infusion, and using a PID controller algorithm to improve brewing consistency. ### Source excerpt This article is about upgrading a regular low cost Espresso machine by adding an ESP32 for both control and connectivity. ## 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 ... ## Adding Compose to Existing Espresso Tests with createEmptyComposeRule() DevFeed: [Adding Compose to Existing Espresso Tests with createEmptyComposeRule()]() Original publisher: [Read original article]() Author: Sam Edwards Published: 2023-04-12T13:46:30Z Content type: tutorial Language: en Sources: [Handstand Sam]() Topics: [Compose](), [Android](), [Instrumentation](), [test]() Tags: [android](), [compose](), [espresso](), [instrumentation](), [test](), [tests](), [updates]() ### AI overview This tutorial explains how to interact with Jetpack Compose elements in existing Android Espresso instrumentation tests without changing the test's existing Activity behavior. It recommends using createEmptyComposeRule() instead of rules that create or launch an Activity. ### Source excerpt As the documentation says, you can combine both Espresso and Compose in an Android instrumentation test. In order to interact with Compose in an instrumentation test you need a ComposeTestRule. Problem Typically you would create a ComposeTestRule with createComposeRule() in a part of your app that is compose only, but that will create a blank [...] ## 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... ## Decreasing Applitools Android Boilerplate with Kotlin and JUnit DevFeed: [Decreasing Applitools Android Boilerplate with Kotlin and JUnit]() Original publisher: [Read original article]() Author: Ben Boral Published: 2019-11-15T17:46:53Z Content type: tutorial Language: en Sources: [RetailMeNot]() Topics: [Testing](), [Boilerplate](), [Kotlin](), [SDKs](), [App]() Tags: [android](), [applitools](), [boilerplate](), [code](), [espresso](), [junit](), [kotlin](), [testing]() ### AI overview This tutorial shows how to reduce boilerplate in Applitools visual regression tests for Android by using Kotlin and JUnit. It describes encapsulating repeated setup and cleanup in a helper and JUnit rule so the test code is more concise and easier to maintain. ### Source excerpt Background At RetailMeNot, we are excited by the promise of automating visual regression tests with Applitools. In this post, I'll show how to make writing Applitools tests for Android a cinch. We'll start with the official integration guide recommendations and then use JUnit and Kotlin features to make our tests concise and maintainable. This post assumes the reader is familiar with Applitools visual testing. Our Starting Point: lots of boilerplate code Applitools's official integration guide for Espresso recommends a test that looks approximately like the below code block. I'll explain each line of this snippet later in the article. But for now, notice the excessive setup code and cleanup code that's getting in the way of our actual test code. This boilerplate would need to be copied for every test. https://medium.com/media/c042e70c7b2c423afde35fc101bc6e31/hrefThe Solution: a much simpler test We can reduce the boilerplate to achieve the following test. By stripping away the setup and cleanup as much as possible, we are left with the kernel of the test. In doing so, the purpose of the test is much easier to comprehend. ApplitoolsHelper, on line 2, has encapsulated the setup and cleanup. This will make long-term maintenance easier, because when the Applitools APIs change, we'll only need to update them in the one location. https://medium.com/media/de1efe74c1f65542057b061fd3b4ad35/hrefThe Required Steps to Run an Applitools Test Before diving into the helper code that enables our concise test, let's review the steps involved in an Applitools visual test: val eyes = Eyes() eyes.apiKey = "YOUR_API_KEY" eyes.appName = "YOUR_APP_NAME" We must initialize the Applitools SDK and set our API key and app name. This is going to be the same for every test in our suite. We will extract this code into a JUnit test rule. eyes.open("TEST_NAME"); This starts the Applitools test session. This must be called with a unique test name for each test. We will use a lambda expression, expl ## Firebase Test Lab December 2017 Update DevFeed: [Firebase Test Lab December 2017 Update]() Original publisher: [Read original article]() Author: Doug Stevenson Published: 2017-12-12T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Android](), [Test coverage](), [test-coverage](), [Testing](), [Script](), [APK](), [App](), [JSON]() Tags: [2017](), [android](), [android-testing](), [apk](), [devices](), [espresso](), [firebase](), [huawei](), [json](), [news](), [screenshots](), [test-coverage](), [test-lab](), [testing](), [update]() ### AI overview Firebase Test Lab's December 2017 update introduces Robo scripts for guiding automated Android tests through specific actions and screens, clusters screenshots by display characteristics, and adds several test devices. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Leveraging The Robot Pattern For Espresso Tests DevFeed: [Leveraging The Robot Pattern For Espresso Tests]() Original publisher: [Read original article]() Author: Adam McNeilly Published: 2017-07-04T00:00:00Z Content type: tutorial Language: en Sources: [Android Essence]() Topics: [Testing](), [Android](), [Development](), [Cheat sheet]() Tags: [android](), [android-development](), [automated](), [cheat-sheet](), [espresso](), [how-to](), [patterns](), [testing](), [tests](), [tutorial]() ### AI overview A tutorial on using the robot pattern to structure Espresso tests for Android applications, making tests easier to write and update as an app changes. It introduces Espresso, reviews core APIs, and demonstrates testing an add-person workflow. ### Source excerpt Espresso is a testing framework for Android that allows developers to write automated tests for their applications. The benefit of automated testing is that you can write a test plan, and simply hit run and have all of the important features in your app tested effortlessly, and arguably more consistent and thorough than manual testing. There is no doubt that it is a lot faster. However, one of the lesser known development patterns for automated testing is the robot pattern, which makes writing tests much easier while providing a painless way to update tests whenever your app changes. Let's take a deeper dive into what makes the robot pattern so powerful, and how to implement it in your next test suite. ## Start using Firebase Test Lab for Android at no charge DevFeed: [Start using Firebase Test Lab for Android at no charge]() Original publisher: [Read original article]() Author: Doug Stevenson Published: 2016-11-17T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Android](), [Development]() Tags: [android](), [espresso](), [firebase](), [google](), [launch](), [test-lab](), [tests]() ### AI overview Firebase Test Lab for Android became available to Firebase Spark and Flame plan users without requiring a credit card or paid Blaze upgrade. Spark and Flame projects received daily quotas for physical and virtual device tests, with limits on devices and test duration. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Customizing the ListView DevFeed: [Customizing the ListView]() Original publisher: [Read original article]() Published: 2014-02-23T07:00:00Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Android](), [Android Studio](), [Testing](), [App](), [Android Library](), [Gradle]() Tags: [android](), [android-library](), [android-studio](), [app](), [espresso](), [gradle](), [testing]() ### AI overview A tutorial on customizing an Android ListView in Android Studio by styling the list, adding sample data, building a custom adapter with custom layouts, and introducing Espresso-based testing through a Gradle project. ### Source excerpt In the last post we created a basic Android project using Android Studio templates. While it's great that we have a fully functioning master/detail style app, it does look a bit bare. In this post, we'll change this by styling our list view, incorporating (sort of) real data to feed our list. We'll make a custom adapter to drive our list with custom layouts, and introduce testing into the mix to ensure that our app continues to perform as expected.