# robolectric Published articles for robolectric. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How We Moved 1,500 Android Screenshot Tests to Roborazzi DevFeed: [How We Moved 1,500 Android Screenshot Tests to Roborazzi]() Original publisher: [Read original article]() Author: Zachary Wander Published: 2026-08-08T05:03:41Z Content type: tutorial Language: en Sources: [Thumbtack Engineering - Medium]() Topics: [screenshot-testing](), [Android](), [Testing](), [Compose](), [Kotlin](), [Firebase](), [Git]() Tags: [android](), [compose](), [consistency](), [firebase](), [git](), [jetpack-compose](), [kotlin](), [mobile](), [robolectric](), [roborazzi](), [screenshot](), [screenshot-testing](), [software-testing](), [technology](), [testing](), [tests]() ### AI overview Thumbtack Engineering describes migrating 1,500 Android screenshot tests from Firebase Test Lab to Roborazzi, which runs locally on the JVM. The article covers porting existing suites, comparing screenshots in Git, and addressing rendering, test-data injection, and dependency-injection differences. ### Source excerpt How we moved 1,500 Android screenshot tests to Roborazzi.Introduction If you're a mobile developer you're probably no stranger to screenshot tests. Making sure that layouts remain consistent as time goes on and code changes is important for ensuring functionality and accessibility. Since Thumbtack uses Kotlin and Jetpack Compose for its Android apps, we had historically been using Firebase Test Lab to capture and compare layouts. However, using Firebase can be slow, tedious, and error-prone, so we decided it was time for a change. Instead of Firebase, we decided to migrate to using Roborazzi, a screenshot testing framework that runs fully locally inside the local JVM instead of relying on remote emulators and devices. For more details on why we migrated and the alternatives we evaluated, check out the previous blog post from Brian. This post is going to go into the details of how we migrated, and the challenges we faced along the way. Porting Loop Because the purpose of screenshot tests is ensuring consistency over time, we wanted to bring over our existing test suites into Roborazzi. Deleting the old ones and just creating new tests as we built new layouts was a potential option, but it would wipe out a lot of our automated verification. Instead, we ported our existing Firebase Test Lab screenshot test suites over to Roborazzi. In general, the porting process was pretty simple: Delete the old screenshots. Move the test suites over from androidTest to test. Adjust the code for any API differences. Record new screenshots. Compare the old and new screenshots in the git diff to make sure nothing is broken. Fix broken screenshots. Since Roborazzi uses Robolectric, and Robolectric implements the Android API, most of the test suites needed very few changes to work, with updating the main test rule and test annotations being enough to get them running. A few, like those that relied on permission granting rules or interacted directly with the test Activity, needed some more ## Headless Screenshot Testing in Thumbtack's Android Apps DevFeed: [Headless Screenshot Testing in Thumbtack's Android Apps]() Original publisher: [Read original article]() Author: Brian Terczynski Published: 2026-03-31T22:47:00Z Content type: tutorial Language: en Sources: [Thumbtack Engineering - Medium]() Topics: [screenshot-testing](), [Testing](), [Android](), [Emulator](), [Firebase](), [Jenkins]() Tags: [android](), [android-app-development](), [emulator](), [firebase](), [jenkins](), [mobile](), [robolectric](), [roborazzi](), [screenshot-testing](), [sdk](), [testing]() ### AI overview Thumbtack explains how it chose Roborazzi to run high-fidelity screenshot tests for its Android apps without an emulator. The article describes how emulator-based testing was slow and difficult to use for Jenkins verification, especially with more than 1,500 tests. ### Source excerpt How we chose Roborazzi for fast, easy, and high-fidelity screenshot tests of our Android apps, without needing to run them on an emulator. As mentioned in our earlier blog post, screenshot tests are a fundamental part of our testing pyramid at Thumbtack. They validate that our UI code renders correctly. They catch UI regressions as our code evolves. They make it easy to share incremental progress with designers. In code reviews, they provide a great way for reviewers to "see" what the UI code is doing. Finally, they are very easy to write! But they were not always easy to run. Because they tested Android UI code, they had to run in a "real" Android environment so that the drawing operations would work. This meant running them on an Android device or emulator. To ensure consistent renderings, developers would have to run their tests on the same device used by our CI job. In the past, this meant having to run a script that would connect to our cloud device testing provider to generate the reference image, which would then be downloaded for inclusion in the local Git branch. Such a process would take minutes to run (not including build time). This got easier when we switched to Firebase Test Lab (FTL), because their emulators were the same as the emulators provided in the Android SDK used on developers' machines. Developers could then simply run their tests on a local emulator which sped up execution time significantly. But it still meant the emulator profile needed to match that of the device on FTL; in particular, the screen size and pixel density. Another problem was, because these were run on an emulator, they could not run with our CR verification job on Jenkins because their execution time was too slow (especially since we have over 1,500 of these tests!). This therefore meant that we had to run our screenshot tests separately, and they could not be used to gate code pushes because they were just too slow to run. So what would often happen was developers would me ## 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 ... ## 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... ## A World Beyond Libraries: Cross-Library screenshot tests on Android DevFeed: [A World Beyond Libraries: Cross-Library screenshot tests on Android]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2023-08-23T21:23:13Z Content type: opinion Language: en Sources: [Sergio's little tech corner]() Topics: [screenshot-testing](), [Android](), [Testing](), [Library]() Tags: [android](), [android-app-development](), [robolectric](), [roborazzi](), [screenshot-testing](), [screenshots](), [testing]() ### AI overview An analysis of Android screenshot-testing libraries, comparing JVM-based approaches such as Paparazzi and Roborazzi with on-device tools. It explains trade-offs involving rendering fidelity, emulator reliability, speed, and platform limitations, including fixes in Robolectric 4.12.1. ### Source excerpt The state of the art of screenshot testing for Android Screenshot testing is trending in Android. Many new libraries have come up, and even Google announced at I/O 20231 that they're working on a new tool for this based on Composable Previews powered... ## Sharing Android Business Logic with iOS Using Doppl and MVP Architecture DevFeed: [Sharing Android Business Logic with iOS Using Doppl and MVP Architecture]() Original publisher: [Read original article]() Published: 2016-12-12T17:00:07Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [cross-platform](), [Mobile](), [backends](), [MVVM](), [Dagger](), [Dependency injection](), [Testing](), [Objective-C]() Tags: [architecture](), [built-by-touchlab](), [code-sharing](), [dagger](), [dependency-injection](), [ios](), [mvvm](), [native](), [open-source](), [press](), [robolectric](), [thoughts]() ### AI overview The article explains Doppl, a set of tools and libraries built around j2objc for sharing Android business logic with iOS while keeping native user interfaces. It discusses applying MVP architecture, adding Dagger for dependency injection, and using sample test runners, while noting that iOS unit tests must currently be run from an Xcode app rather than the command line. ### Source excerpt Are you building a product and decided to build native? Do you have some no trivial business logic? If so then be sure to read this latest post. ## Better Android Testing with Robolectric 2.0 DevFeed: [Better Android Testing with Robolectric 2.0]() Original publisher: [Read original article]() Author: Square Engineering Published: 2013-05-09T16:03:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Testing](), [Android](), [Framework](), [Mocking](), [Instrumentation](), [ide](), [releases]() Tags: [android](), [android-testing](), [announce](), [availability](), [bugs](), [engineering](), [fragments](), [framework](), [ide](), [instrumentation](), [mocking](), [robolectric](), [testing]() ### AI overview This article announces Robolectric 2.0 release candidate 1 and explains how the framework supports Android unit testing on a desktop JVM. It describes improved Android OS emulation using modified Android SDK code, support for styles, themes, and system resources, faster test startup, and bug fixes. ### Source excerpt The essential framework for testing Android applications ## The Resurrection of Testing for Android DevFeed: [The Resurrection of Testing for Android]() Original publisher: [Read original article]() Author: Square Engineering Published: 2013-04-03T16:02:00Z Content type: tutorial Language: en Sources: [Jake Wharton](), [Square Corner Blog RSS Feed]() Topics: [Testing](), [Android](), [Framework](), [Development]() Tags: [android](), [engineering](), [instrumentation](), [junit](), [performance](), [robolectric](), [testing](), [tests](), [unit-tests]() ### AI overview This article explains Android testing challenges caused by empty API jars and presents Robolectric as a framework that replaces those stubs with actual code. It demonstrates using Robolectric with JUnit to test layouts, views, activities, and UI interactions, and notes improvements planned for version 2. ### Source excerpt An oft-overlooked aspect of development gets a fresh look.