Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.36.0
->1.38.0
1.36.0
->1.38.0
1.36.0
->1.38.0
1.36.0
->1.38.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
takahirom/roborazzi (io.github.takahirom.roborazzi:roborazzi-junit-rule)
v1.38.0
Compare Source
Bugfix
Fix: Bug preventing the revival of deleted screenshot images
Thanks to @pedromfmachado's contribution, we've addressed a bug where deleted screenshot test images would be erroneously revived. Previously, when screenshot tests were removed and their corresponding images deleted from the output directory, running the
record
task again would cause the Roborazzi Gradle task to recreate the removed images. While this could be temporarily resolved withroborazzi.cleanupOldScreenshots=true
, that approach was undesirable as it would also remove images when test filters were used. This was a complex issue to solve, and we extend our gratitude to @pedromfmachado for the fix.Fix: Made screenshot dump deterministic
We have a dump feature that allows us to check the properties or hierarchy of views or composables in an image. We sorted the properties to ensure a deterministic output. Thanks to @siarhei-luskanau for this contribution.
New Feature
Feature: Added
RoborazziComposeActivityThemeOption
Previously, changing the theme of
RoborazziTransparentActivity
was not possible. We have now deprecatedRoborazziTransparentActivity
and renamed it toRoborazziActivity
. Additionally, we addedRoborazziComposeActivityThemeOption
to enable changing the Activity's theme. Thank you again, @pedromfmachado, for this feature.You can now change the Activity theme like this:
What's Changed
New Contributors
Full Changelog: takahirom/roborazzi@1.37.0...1.38.0
v1.37.0
Compare Source
Bug Fixes and Workarounds
Compose AlertDialog Support
Support for capturing Alert Dialogs has been fixed, ensuring correct screenshot display.
captureScreenRoboImage()
, which merges all windows, is now used only when multiple windows are present. Thanks to @ashughes for reporting this and to @mhidaka and @hiroaki404 for bringing it to my attention at a Japan Android testing event.Workaround for Overlap Handling for SDK 35 Compose Screenshots
Problem
When updating to SDK 35 and using the default theme, the ActionBar is included in screenshots, leading to overlap when using
createComposeRule()
. This occurs becausecreateComposeRule()
uses the default theme by default. Thank you for letting me know about this, @keyboardsurfer!I have filed an issue for this: https://issuetracker.google.com/issues/383368165
Why this happens
SDK 35 enforces edge-to-edge display, which means it does not provide automatic padding for the ActionBar.
How Roborazzi currently workarounds this
Roborazzi now automatically hides the ActionBar when taking screenshots on SDK 35 and higher. This functions similarly to
view.getActivity()?.actionBar?.hide()
. However, this workaround may cause performance issues and should not be relied upon. Roborazzi outputs warning logs with alternative suggestions. Thank you to @sergio-sastre for advising on this workaround!If you need to include the ActionBar in screenshots, Roborazzi provides a flag,
roborazzi.compose.actionbar.overlap.fix=false
, that can be added to yourgradle.properties
file.What should we do?
A permanent solution will likely require changes from Google. In the meantime, adding
<application android:theme="@​style/android:Theme.Material.Light.NoActionBar" />
to the module'ssrc/test/AndroidManifest.xml
file changes the Activity's default theme and resolves the issue. Thank you to @mattinger for finding this!https://github.com/takahirom/roborazzi/issues/598#issuecomment-2533372700
Stabilized Output for Dump Screenshots
Thanks to @siarhei-luskanau for contributing an improvement that reduces unnecessary diffs for the Roborazzi dump feature.
New Features
Add
inspectionMode()
for Compose PreviewsThanks to @YusukeMoriJapan's contribution,
inspectionMode()
is now available inRoborazziComposeOptions
. This is particularly useful when working with libraries that have specific preview implementations. This mode is off by default to maintain high fidelity.Here's how to enable it:
What's Changed
New Contributors
Full Changelog: takahirom/roborazzi@1.36.0...1.37.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.