fix(deps): update roborazzi to v1.54.0 #2489
Merged
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.52.0→1.54.01.52.0→1.54.01.52.0→1.54.01.52.0→1.54.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
takahirom/roborazzi (io.github.takahirom.roborazzi)
v1.54.0Compare Source
Breaking change: Report HTML and JSON paths have changed
The HTML report used to be at
build/reports/roborazzi/index.htmlbut is now located atbuild/reports/roborazzi/<build_variant>/index.html. This is a first step toward fixing a long-standing issue where runningrecordRoborazzi(instead ofrecordRoborazziDebug) could break test results; further work is still needed to make it fully reliable.You should be able to fix it by adding
/debug/(or your build variant) to the path in your CI script. I believe the change is straightforward, but if you run into any cases where it's difficult please let me know.Note: This change does not affect the paths of the generated screenshot images, so most users will not be impacted.
Thank you for your contribution, @vladcudoidem!
Behavioral change: Fixed screenshot timing for Compose Preview Support
Previously, we used Espresso.onIdle() and ShadowLooper.idle(), but these APIs are not suitable for Compose. Consequently, screenshots could not be captured after onSizeChanged completed.
If you encounter issues with infinite animations—such as
CircularProgressIndicator—you can configure frame-based captures using@RoboComposePreviewOptions.Thank you for reporting this issue, @savvasenok!
What's Changed
Full Changelog: takahirom/roborazzi@1.53.0...1.54.0
v1.53.0Compare Source
New feature
generatedTestClassCountand behavior changes to Compose Preview supportWe've added the
generatedTestClassCountoption, which enables us to run Preview tests in parallel when you set maxParallelForks to a value greater than 1.As the name
generatedTestClassCountsuggests, this option generates as many test classes as specified. It creates tests whosepreviewIndex % totalTestClassCount == testClassIndex. However, this option does not modify maxParallelForks, so you must also set maxParallelForks yourself to run tests in parallel. This is our policy: we never alter other plugin(AGP) settings in order to keep one single source of configuration.Behavior changes: generatedTestClassCount now defaults to the same value as maxParallelForks. Therefore, if you already use maxParallelForks during testing, the behavior may change if your tests are non-deterministic—for example, if they depend on the order in which other tests run.
Last but not least, thanks to @sergio-sastre for suggesting this feature, reviewing the code, and confirming the approach works!
Fix configuration-time resolution when using BOM to Compose Preview support
Fixed an error where the version verification logic triggered configuration-time resolution errors when using BOM (Bill of Materials) for dependency management.
The fix simplifies the
verifyComposablePreviewScannerVersionmethod by removing the complex fallback logic that attempted to infer versions from test configurations. Instead, the plugin now only checks explicitly declared versions—when no version is specified (indicating BOM management), verification is skipped.Thanks to @igokoro for reporting this issue!
Fix iOS snapshot not creating parent directories before writing files
Fixed a critical bug where iOS snapshot tests weren't being recorded on the first run. The root cause was that
NSData.writeToFilesilently fails when parent directories don't exist.The fix ensures parent directories are automatically created before writing files using
NSFileManager.defaultManager.createDirectoryAtPathwithwithIntermediateDirectories = true. Additionally, error logging was added to report both successful and failed file operations, preventing silent failures.Thanks to @jl-jonas for reporting this issue!
What's Changed
34e1148by @renovate[bot] in #764Full Changelog: takahirom/roborazzi@1.52.0...1.53.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot.