Update roborazzi to v1.36.0 #110
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #110 +/- ##
=======================================
Coverage 84.11% 84.11%
=======================================
Files 23 23
Lines 2821 2821
Branches 252 252
=======================================
Hits 2373 2373
Misses 221 221
Partials 227 227 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/roborazzi
branch
from
a8433ec to
f2fde0a
Compare
renovate
bot
force-pushed
the
renovate/roborazzi
branch
from
f2fde0a to
ebaf5a2
Compare
renovate
bot
force-pushed
the
renovate/roborazzi
branch
from
ebaf5a2 to
e80c616
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.32.2->1.36.01.32.2->1.36.01.32.2->1.36.01.32.2->1.36.0Release Notes
takahirom/roborazzi (io.github.takahirom.roborazzi)
v1.36.0Compare Source
Behavior Changes to
roborazzi.outputDir.set(file("somedir"))inbuild.gradlePreviously, when modifying
roborazzi.outputDir, such as setting it tosrc/screenshots, this option also affected the paths for comparison images, likefoo_compare.png. This behavior often caused issues, such as unintentionally saving comparison images to version control systems (e.g., Git). To address this, we have discontinued this behavior. Comparison images are now saved inbuild/outputs/roborazziby default, while the behavior for reference images remains unchanged.For users who wish to customize the path for comparison images, we have introduced a new option:
roborazzi.compare.outputDir.While I don't believe there are strong use cases for this, if you want to save the comparison images in a custom directory as you did before, you can specify
roborazzi.compare.outputDiras follows:roborazzi { outputDir.set(file("src/screenshots")) compare { outputDir.set(file("src/screenshots")) } }I believe this adjustment will be highly beneficial for most use cases involving changes to
outputDir.What's Changed
Full Changelog: takahirom/roborazzi@1.35.0...1.36.0
v1.35.0Compare Source
Add support for heightDp, widthDp, showBackground, and backgroundColor of Compose Preview parameters
We have introduced Experimental Compose Preview Support in 1.22.0, but it does not yet support all parameters of the
@Previewannotation. Thanks to @sergio-sastre 's pull request, the Experimental Compose Preview Support now includes support for heightDp, widthDp, showBackground, and backgroundColor.Introduce RoborazziComposeOptions
To accommodate the changes in preview parameters, we’ve made the API more flexible.
We’ve added the
RoborazziComposeOptionsparameter toComposablePreview<AndroidPreviewInfo>.captureRoboImage()and the composable function version,captureRoboImage{}. Previously, the API was limited; for example, you couldn’t access the ActivityScenario or the composable function directly. Now, you have full control over these components. Thank you for your code review @sergio-sastreHere’s an example of a custom option:
captureRoboImage( roborazziComposeOptions = RoborazziComposeOptions { // We have several options to configure the test environment. fontScale(2f) // We can also configure the activity scenario and the composable content. addOption( object : RoborazziComposeComposableOption, RoborazziComposeActivityScenarioOption { override fun configureWithActivityScenario(scenario: ActivityScenario<out Activity>) { scenario.onActivity { it.window.decorView.setBackgroundColor(Color.BLUE) } } override fun configureWithComposable(content: @​Composable () -> Unit): @​Composable () -> Unit { return { Box(Modifier .padding(10.dp) .background(color = androidx.compose.ui.graphics.Color.Red) .padding(10.dp) ) { content() } } } } ) }, ) { Text("Hello Compose!") }Breaking Change:
fun ComposablePreview<AndroidPreviewInfo>.applyToRobolectricConfiguration()is now deprecated and marked as an errorAs part of our updates to how composables are configured, the
applyToRobolectricConfiguration()function is now deprecated and marked as an error. Instead, you can use one of the following alternatives:previewInfo.toRoborazziComposeOptions().apply(scenario, composeContent)ComposablePreview<AndroidPreviewInfo>.captureRoboImage(roborazziComposeOptions)We believe this feature is not widely used, and the migration should be straightforward. However, if you encounter any issues, please don’t hesitate to reach out.
What's Changed
Full Changelog: takahirom/roborazzi@1.34.0...1.35.0
v1.34.0Compare Source
Stabilize RoborazziOptions and RoborazziRule.Options
RoborazziOptions and RoborazziRule.Options were not annotated with
ExperimentalRoborazziApi, but their constructor parameters had the annotation. This causedExperimentalRoborazziApito be unintentionally exposed. To address this, we have separated constructors for stable parameters. Additionally, within Roborazzi samples, we have enabledallWarningsAsErrors = trueto ensure that any unexpected exposure can be promptly identified.Thank you for reporting this issue and for your code review, @colinrtwhite!
Fixes for Accessibility Checks
We introduced Experimental Accessibility Test Framework checks in version 1.33.0.
Thanks to @yschimke's contribution, several fixes have been implemented for accessibility checks, including check suppression and improved logging.
What's Changed
Full Changelog: takahirom/roborazzi@1.33.0...1.34.0
v1.33.0Compare Source
Experimental Accessibility Test Framework checks
Thanks to @yschimke's contribution, we now have a library that integrates accessibility checks into Roborazzi. It uses the Accessibility Test Framework to ensure accessibility.
Please add the library dependency:
testImplementation("io.github.takahirom.roborazzi:roborazzi-accessibility-check:[version]")https://github.com/takahirom/roborazzi/tree/main/roborazzi-accessibility-check
Configure in Junit Rule
Add accessibility checks
Not only is this library designed to make our app accessible to everyone, but I also believe that AI agent testing will be a future trend, and we want to prepare for it. I think this could help make our app accessible to AI as well, enabling agents to interact with it, such as clicking on image buttons using content descriptions. Additionally, we can create custom checks, like NoRedTextCheck, specifically for AI.
What's Changed
Full Changelog: takahirom/roborazzi@1.32.2...1.33.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.