Switch from Roborazzi to Paparazzi for snapshot testing by runningcode · Pull Request #767 · EmergeTools/hackernews

runningcode · 2026-03-18T15:59:57Z

Replace Roborazzi plugin with Paparazzi for snapshot generation and wire it to sentry.

This PR also updates to JDK 21 and Gradle 9.1 because paparazzi requires them.

🤖 Generated with Claude Code

sentry · 2026-03-18T16:02:18Z

android/app/build.gradle.kts

-  )
+afterEvaluate {
+  tasks.named<SentryUploadSnapshotsTask>("sentryUploadSnapshotsRelease") {
+    dependsOn("recordPaparazziDebug")


Bug: The sentryUploadSnapshotsRelease task incorrectly depends on recordPaparazziDebug, causing a build variant mismatch that could mask release-specific visual bugs.
_{Severity: MEDIUM}

Suggested Fix

Change the dependency for the sentryUploadSnapshotsRelease task from tasks.named("recordPaparazziDebug") to tasks.named("recordPaparazziRelease") to ensure snapshots from the correct build variant are generated and uploaded.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: android/app/build.gradle.kts#L140 Potential issue: The Gradle configuration sets up the `sentryUploadSnapshotsRelease` task to depend on `recordPaparazziDebug`. This creates a mismatch between build variants, where the task for uploading release snapshots is triggered by the generation of debug snapshots. Since debug and release builds can have different configurations (e.g., minification, application ID suffix), the snapshots generated by the debug task may not accurately represent the visual appearance of the release app. This could lead to visual regressions specific to the release build being missed during automated testing, as debug-generated snapshots are uploaded to Sentry's release channel.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

sentry · 2026-03-18T16:05:03Z

android/app/build.gradle.kts

+//  testImplementation(libs.robolectric)
+//  testImplementation(libs.roborazzi)
+//  testImplementation(libs.roborazzi.compose)
+//  testImplementation(libs.roborazzi.rule)


Bug: Roborazzi dependencies are commented out, but tests still use its API, which will cause compilation failure and break the snapshot generation pipeline.
_{Severity: CRITICAL}

Suggested Fix

Migrate the existing snapshot tests from the Roborazzi API to the Paparazzi API. This includes replacing calls like captureRoboImage() with paparazzi.snapshot() and updating the test class setup to use the Paparazzi JUnit rule instead of the Robolectric test runner.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: android/app/build.gradle.kts#L177-L180 Potential issue: The build configuration was updated to use Paparazzi for snapshot testing, and the corresponding Roborazzi dependencies were commented out in `android/app/build.gradle.kts`. However, test files like `BookmarksScreenComposeTest.kt` and `StoryRowComposeTest.kt` were not migrated and still use the Roborazzi API, such as `captureRoboImage()`. This mismatch will cause the test suite to fail compilation because the necessary dependencies are missing. As a result, the `recordPaparazziDebug` Gradle task will not generate any snapshots, breaking the snapshot testing and upload pipeline.

android/app/build.gradle.kts

sentry · 2026-03-19T07:48:23Z

android/app/build.gradle.kts

+    snapshotsPath.fileProvider(testTask.map { task ->
+      task.outputs.files.files.first { it.name == "snapshots" }
+    })


Bug: The sentryUploadSnapshotsRelease task will fail because it tries to find a "snapshots" directory from test outputs that no longer exist, causing the CI build to crash.
_{Severity: CRITICAL}

Suggested Fix

Since the Paparazzi tests have been removed, the sentryUploadSnapshotsRelease task configuration in android/app/build.gradle.kts and its corresponding invocation in the .github/workflows/android_emerge_snapshots.yml CI workflow should be deleted to prevent build failures.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: android/app/build.gradle.kts#L139-L141 Potential issue: The `sentryUploadSnapshotsRelease` Gradle task is configured to locate a "snapshots" directory within the outputs of the `testDebugUnitTest` task by calling `.first { it.name == "snapshots" }`. However, the Paparazzi tests responsible for generating these snapshots have been removed in this pull request. As a result, no "snapshots" directory will be found in the task's outputs. This will cause the `.first()` call to throw a `NoSuchElementException`, leading to a build failure whenever the CI workflow invokes this task.

sentry · 2026-03-19T07:56:04Z

android/app/build.gradle.kts

+    snapshotsPath.fileProvider(testTask.map { task ->
+      task.outputs.files.files.first { it.name == "snapshots" }
+    })


Bug: The sentryUploadSnapshotsRelease task will fail because it incorrectly searches for the "snapshots" directory in the testDebugUnitTest task's outputs, where it doesn't exist.
_{Severity: CRITICAL}

Suggested Fix

Instead of searching the testDebugUnitTest task's outputs, the snapshotsPath should be configured to point directly to the source-controlled snapshot directory. Use project.file("src/test/snapshots") to correctly reference the path.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: android/app/build.gradle.kts#L139-L141 Potential issue: The `sentryUploadSnapshotsRelease` task is configured to find the Paparazzi snapshots path by searching the outputs of the `testDebugUnitTest` task for a directory named `"snapshots"`. However, Paparazzi snapshots are stored in the source directory `src/test/snapshots/`, which is not registered as an output of the test task. Consequently, the `.first { it.name == "snapshots" }` call will find no matching file and throw a `NoSuchElementException` at runtime. This will cause the Gradle build to fail, specifically breaking CI/CD workflows that depend on this task.

emerge-tools · 2026-03-19T07:57:48Z

🛰️ Build Distribution

Build available for installation

App Name	App ID	Platform	Version	Tag	Install Page
Hacker News	com.emergetools.hackernews	android	1.0.6	release	🔗 Install Build

🛸 Powered by Emerge Tools

sentry · 2026-03-19T07:57:58Z

Sentry Build Distribution

App Name	App ID	Version	Configuration	Install Page
Hacker News	com.emergetools.hackernews	1.0.6 (17)	release	Install Build

sentry · 2026-03-19T07:59:44Z

.github/workflows/android_emerge_snapshots.yml

+      - name: Generate Paparazzi snapshots
+        run: ./gradlew :app:recordPaparazziDebug :app:sentryUploadSnapshotsRelease


Bug: The CI workflow runs recordPaparazziDebug, but all snapshot tests have been removed. This results in zero snapshots being generated, effectively disabling snapshot testing.
_{Severity: HIGH}

Suggested Fix

Re-implement the deleted snapshot tests using the Paparazzi framework. Create new test files with @Test annotated methods that use the Paparazzi rule to capture snapshots of the relevant composables. This will ensure the recordPaparazziDebug task generates the expected snapshots.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: .github/workflows/android_emerge_snapshots.yml#L65-L66 Potential issue: The pull request migrates the snapshot testing framework from Roborazzi to Paparazzi. However, while the CI workflow in `.github/workflows/android_emerge_snapshots.yml` is updated to run the `recordPaparazziDebug` task, all existing snapshot test files were removed without any Paparazzi-compatible replacements being added. As a result, the `recordPaparazziDebug` task will execute successfully but will generate zero snapshots because there are no `@Test` methods to drive the process. This silently disables the entire snapshot testing pipeline, defeating its purpose.

android/app/build.gradle.kts

emerge-tools · 2026-03-19T08:38:31Z

📸 Snapshot Test

Base build not found

No build was found for the base commit 70e95cf. This is required to generate a snapshot diff for your pull request.

It's possible that you created a branch off the base commit before all of the CI steps have finished processing, e.g. the one that uploads a build to our system. If that's the case, no problem! Just wait and this will eventually resolve.

🛸 Powered by Emerge Tools

android/app/build.gradle.kts

runningcode · 2026-03-19T16:43:06Z

.github/workflows/android_beta_build.yml

        uses: actions/setup-java@v5
        with:
-          java-version: "17"
+          java-version: "21"


paparazzi 2.0.0-alpha4 requires jdk 21.

runningcode · 2026-03-19T16:43:45Z

android/gradle/wrapper/gradle-wrapper.properties

 distributionBase=GRADLE_USER_HOME
 distributionPath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions/gradle-8.14.4-bin.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-9.1.0-bin.zip


paparazzi requires Gradle 9.1+

Replace Roborazzi with Paparazzi for snapshot generation and wire the sentryUploadSnapshotsRelease task to consume Paparazzi's output directory. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Instead of hardcoding the snapshot directory path, use the output directory registered by Paparazzi on testDebugUnitTest. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Instead of fragile name matching on "snapshots", use the registered property name "paparazzi.snapshots.output.dir" to find the output dir. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

The Gradle public API doesn't expose task output properties by name. The withPropertyName API is only for up-to-date checking, not lookup. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

sentry bot reviewed Mar 18, 2026

View reviewed changes

android/app/build.gradle.kts Show resolved Hide resolved

sentry bot reviewed Mar 19, 2026

View reviewed changes

android/app/build.gradle.kts Show resolved Hide resolved

runningcode force-pushed the no/switch-roborazzi-to-paparazzi branch from 5305a6a to 18adf8b Compare March 19, 2026 07:46

sentry bot reviewed Mar 19, 2026

View reviewed changes

android/app/build.gradle.kts Show resolved Hide resolved

sentry bot reviewed Mar 19, 2026

View reviewed changes

android/app/build.gradle.kts Show resolved Hide resolved

runningcode commented Mar 19, 2026

View reviewed changes

runningcode and others added 8 commits March 20, 2026 10:49

fix(android): Switch from Roborazzi to Paparazzi for snapshot testing

613f505

Replace Roborazzi with Paparazzi for snapshot generation and wire the sentryUploadSnapshotsRelease task to consume Paparazzi's output directory. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix(android): Update SAGP to 6.3.0-alpha.02

21c4836

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix(android): Wire snapshotsPath to Paparazzi test task output

31d687e

Instead of hardcoding the snapshot directory path, use the output directory registered by Paparazzi on testDebugUnitTest. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix(android): Revert SAGP to 6.3.0-alpha.01

14e46cb

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix(android): Switch snapshot workflow from Roborazzi to Paparazzi

45ad3d1

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix(android): Upgrade Gradle wrapper from 8.14.4 to 9.1.0

d6913bb

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix(android): Use Paparazzi's named output property for snapshots path

bd92488

Instead of fragile name matching on "snapshots", use the registered property name "paparazzi.snapshots.output.dir" to find the output dir. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix(android): Revert snapshots path lookup to original approach

57e8120

The Gradle public API doesn't expose task output properties by name. The withPropertyName API is only for up-to-date checking, not lookup. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

runningcode force-pushed the no/switch-roborazzi-to-paparazzi branch from 7057c21 to 57e8120 Compare March 20, 2026 09:52

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Switch from Roborazzi to Paparazzi for snapshot testing#767

Switch from Roborazzi to Paparazzi for snapshot testing#767
runningcode wants to merge 8 commits intomainfrom
no/switch-roborazzi-to-paparazzi

runningcode commented Mar 18, 2026 •

edited

Loading

Uh oh!

sentry bot Mar 18, 2026

Uh oh!

sentry bot Mar 18, 2026

Uh oh!

Uh oh!

Uh oh!

sentry bot Mar 19, 2026

Uh oh!

sentry bot Mar 19, 2026

Uh oh!

emerge-tools bot commented Mar 19, 2026 •

edited

Loading

Uh oh!

sentry bot commented Mar 19, 2026 •

edited

Loading

Uh oh!

sentry bot Mar 19, 2026

Uh oh!

Uh oh!

emerge-tools bot commented Mar 19, 2026 •

edited

Loading

Uh oh!

Uh oh!

runningcode Mar 19, 2026

Uh oh!

runningcode Mar 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

		- name: Generate Paparazzi snapshots
		run: ./gradlew :app:recordPaparazziDebug :app:sentryUploadSnapshotsRelease

Conversation

runningcode commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

sentry bot Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

sentry bot Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

sentry bot Mar 19, 2026

Choose a reason for hiding this comment

Uh oh!

sentry bot Mar 19, 2026

Choose a reason for hiding this comment

Uh oh!

emerge-tools bot commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🛰️ Build Distribution

Build available for installation

Uh oh!

sentry bot commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Sentry Build Distribution

Uh oh!

sentry bot Mar 19, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

emerge-tools bot commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📸 Snapshot Test

Base build not found

Uh oh!

Uh oh!

runningcode Mar 19, 2026

Choose a reason for hiding this comment

Uh oh!

runningcode Mar 19, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

runningcode commented Mar 18, 2026 •

edited

Loading

emerge-tools bot commented Mar 19, 2026 •

edited

Loading

sentry bot commented Mar 19, 2026 •

edited

Loading

emerge-tools bot commented Mar 19, 2026 •

edited

Loading