-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update test.roborazzi to v1.36.0 #829
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/test.roborazzi
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
force-pushed
the
renovate/test.roborazzi
branch
2 times, most recently
from
August 17, 2023 19:45
71edbfc
to
37679f0
Compare
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
3 times, most recently
from
August 26, 2023 06:16
d69422f
to
767e6bc
Compare
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
6 times, most recently
from
September 6, 2023 22:35
91741b8
to
aea3340
Compare
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
4 times, most recently
from
September 14, 2023 18:12
47c80b8
to
6f0fb26
Compare
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
2 times, most recently
from
September 18, 2023 07:17
8ba7e81
to
7ae5a9c
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.4.0
chore(deps): update test.roborazzi to v1.5.0
Sep 18, 2023
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
3 times, most recently
from
September 25, 2023 12:14
1f0f766
to
ef8b1f5
Compare
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
3 times, most recently
from
October 6, 2023 18:24
69b04cb
to
04f0f71
Compare
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
October 8, 2023 06:51
04f0f71
to
e3a9d1d
Compare
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
August 6, 2024 04:49
5fb29d8
to
d5a0d9d
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.25.0
chore(deps): update test.roborazzi to v1.26.0
Aug 6, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
October 2, 2024 04:08
d5a0d9d
to
e46498c
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.26.0
chore(deps): update test.roborazzi to v1.27.0
Oct 2, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
October 6, 2024 07:08
e46498c
to
b604660
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.27.0
chore(deps): update test.roborazzi to v1.28.0
Oct 6, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
October 13, 2024 10:25
b604660
to
04bfaf6
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.28.0
chore(deps): update test.roborazzi to v1.29.0
Oct 13, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
November 3, 2024 13:46
04bfaf6
to
753c174
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.29.0
chore(deps): update test.roborazzi to v1.30.0
Nov 3, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
November 4, 2024 03:41
753c174
to
44c2d4e
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.30.0
chore(deps): update test.roborazzi to v1.30.1
Nov 4, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
November 5, 2024 13:42
44c2d4e
to
8281530
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.30.1
chore(deps): update test.roborazzi to v1.31.0
Nov 5, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
November 7, 2024 05:09
8281530
to
f652ef4
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.31.0
chore(deps): update test.roborazzi to v1.32.0
Nov 7, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
November 7, 2024 07:39
f652ef4
to
8ce9c5b
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.32.0
chore(deps): update test.roborazzi to v1.32.1
Nov 7, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
November 9, 2024 01:28
8ce9c5b
to
84f5148
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.32.1
chore(deps): update test.roborazzi to v1.32.2
Nov 9, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
November 21, 2024 11:25
84f5148
to
106d72e
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.32.2
chore(deps): update test.roborazzi to v1.33.0
Nov 21, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
November 24, 2024 03:51
106d72e
to
aceeff4
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.33.0
chore(deps): update test.roborazzi to v1.34.0
Nov 24, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
December 8, 2024 04:54
aceeff4
to
4e55895
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.34.0
chore(deps): update test.roborazzi to v1.35.0
Dec 8, 2024
renovate
bot
force-pushed
the
renovate/test.roborazzi
branch
from
December 9, 2024 11:49
4e55895
to
df22b21
Compare
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.35.0
chore(deps): update test.roborazzi to v1.36.0
Dec 9, 2024
renovate
bot
changed the title
chore(deps): update test.roborazzi to v1.36.0
fix(deps): update test.roborazzi to v1.36.0
Dec 10, 2024
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.3.0
->1.36.0
1.3.0
->1.36.0
1.3.0
->1.36.0
1.3.0
->1.36.0
Release Notes
takahirom/roborazzi (io.github.takahirom.roborazzi)
v1.36.0
Compare Source
Behavior Changes to
roborazzi.outputDir.set(file("somedir"))
inbuild.gradle
Previously, 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/roborazzi
by 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.outputDir
as follows: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.0
Compare 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
@Preview
annotation. 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
RoborazziComposeOptions
parameter 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:
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.
Breaking Change: Composable
captureRoboImage{}
Behavior ChangeWe intended to use a transparent background for the Compose
captureRoboImage
function, but it was not applied due to Robolectric's resource merging mechanism. We have fixed this behavior; however, this change will result in altered screenshots. You can now specify the background in the newRoborazziComposeOptions
as we had previously.What's Changed
Full Changelog: takahirom/roborazzi@1.34.0...1.35.0
v1.34.0
Compare Source
Stabilize RoborazziOptions and RoborazziRule.Options
RoborazziOptions and RoborazziRule.Options were not annotated with
ExperimentalRoborazziApi
, but their constructor parameters had the annotation. This causedExperimentalRoborazziApi
to be unintentionally exposed. To address this, we have separated constructors for stable parameters. Additionally, within Roborazzi samples, we have enabledallWarningsAsErrors = true
to 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.0
Compare 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
v1.32.2
Compare Source
WebP Image Comparison Improvements
Improved handling for transparent pixels in WebP image comparisons. Previously, transparent pixels in WebP images were sometimes returned with unexpected color values (e.g., r = 1, g = 0, b = 0, a = 0), which caused inconsistencies in image comparisons. The comparison logic now correctly handles transparent pixels by interpreting them as fully transparent black (r = 0, g = 0, b = 0, a = 0) to ensure consistent results across comparisons.
Special thanks to @ArcaNO93 for identifying and reporting this issue!
What's Changed
Full Changelog: takahirom/roborazzi@1.32.1...1.32.2
v1.32.1
Compare Source
Experimental WebP support and other image formats
Now, you can set
roborazzi.record.image.extension
towebp
in yourgradle.properties
file to generate WebP images.roborazzi.record.image.extension=webp
To enable WebP support, add
testImplementation("io.github.darkxanter:webp-imageio:0.3.3")
to yourbuild.gradle.kts
file.WebP is a lossy image format by default, which can make managing image differences challenging. To address this, we provide a lossless WebP image feature.
WebP lossless images are reported to be 26% smaller in size compared to PNGs.
You can also use other image formats by implementing your own
AwtImageWriter
andAwtImageLoader
.Thank you, @ArcaNO93, for providing this suggestion and the code review!
Adjustments to AI-Powered Image Assertion
In version 1.30.0, we introduced Roborazzi AI-Powered Image Assertion.
We made some adjustments to the AI-Powered Image Assertion
InternalRoborazziApi
despite being documented in the README. We have now changed it to ExperimentalRoborazzi API.Changes from 1.32.0
API Key Masking in Logs for OpenAiAiAssertionModel
For users enabling logging through
OpenAiAiAssertionModel.loggingEnabled
, API keys in log outputs are now masked to improve security. Previously, API keys could appear in logs, which could unintentionally expose them, especially in test reports. With this update, sensitive data is automatically masked, helping users avoid accidental exposure.What's Changed
Full Changelog: takahirom/roborazzi@1.31.0...1.32.1
v1.32.0
Compare Source
Please refer to the 1.32.1 release at https://github.com/takahirom/roborazzi/releases/tag/1.32.1
v1.31.0
Compare Source
Added Experimental Support for Cleaning Up Old Screenshots
This release introduces the
roborazzi.cleanupOldScreenshots=true
option ingradle.properties
, allowing users to automatically remove outdated screenshots. By default, this is set tofalse
to prevent accidental deletions when running filtered tests. Please note that enabling this option may result in unintended deletions when running filtered tests. You can use-Proborazzi.cleanupOldScreenshots=true
for CI configurations to clean up screenshots only in CI runs without affecting local settings.This cleanup implementation may affect the cache mechanism. We have some integration tests in place, but if you notice any issues, please let us know.
Thank you, @JackEblan, for suggesting the cleanup feature!
Improve AI Assertion Error Message
In the previous release, we introduced Roborazzi AI-Powered Image Assertion.
When an AI assertion fails, it’s important to review the screenshots to understand what went wrong with the images. Therefore, I enhanced the error message to include the file paths of the images.
What's Changed
Full Changelog: takahirom/roborazzi@1.30.1...1.31.0
v1.30.1
Compare Source
Roborazzi AI-Powered Image Assertion 🤖 ✨
Roborazzi introduces an experimental AI-powered image assertion feature to simplify and scale the process of verifying screenshot test content. This feature helps automate tedious visual checks by comparing images based on customizable AI prompts, utilizing either the Gemini API or OpenAI API. It only activates when images differ, conserving resources. Additionally, manual AI assertion is available, allowing users to leverage local language models without external dependencies.
We don't include Gemini or OpenAI dependencies in the
roborazzi
module. To use these models, you can add eitherroborazzi-ai-gemini
orroborazzi-ai-openai
as dependencies.For more information, please check out this documentation page:
https://takahirom.github.io/roborazzi/ai-powered-image-assertion.html
Roborazzi Compose Preview Support now supports the device parameter
@Preview(device = "")
📱Roborazzi Compose Preview Support uses ComposablePreviewScanner and ComposablePreviewScanner now supports parsing device parameter. It is introduced to Compose Preview Support. Thank you, @sergio-sastre, for developing this adapter and integrating it with Roborazzi.
If you are using Roborazzi Compose Preview Support with device parameters, you need to update your ComposablePreviewScanner to version 0.4.0.
Remove Context Receiver from roborazzi-desktop ♻️
The Context Receiver in Kotlin is now deprecated, so we need to remove it. The
context(DesktopComposeUiTest)
requirement existed because the filecompose/ui/ui-test/src/skikoMain/kotlin/androidx/compose/ui/test/SkikoImageHelpers.kt
was previously unavailable, necessitating the use of DesktopComposeUiTest. Now that SkikoImageHelpers is available, we can eliminate thecontext(DesktopComposeUiTest)
requirement.This functionality was introduced in the Compose Multiplatform core repository (commit
1664fba
: JetBrains/compose-multiplatform-core@1664fba) and has been supported since Compose Multiplatform version 1.5.12 (https://github.com/JetBrains/compose-multiplatform-core/releases/tag/v1.5.12).Please note that this may be a breaking change if you are using Compose Multiplatform version 1.5.12 or earlier.
Changes from 1.30.0
Breaking changes to 1.30.0:
Renamed parameter
assertPrompt
toassertionPrompt
.Use
max_tokens
instead ofmax_completion_tokens
for the OpenAI API:Although
max_tokens
has been deprecated, we still need to use it in certain environments.What's Changed
eef6144
by @renovate in https://github.com/takahirom/roborazzi/pull/509b4b15b8
by @renovate in https://github.com/takahirom/roborazzi/pull/51011bd719
by @renovate in https://github.com/takahirom/roborazzi/pull/519assertPrompt
toassertionPrompt
by @takahirom in https://github.com/takahirom/roborazzi/pull/535New Contributors
Full Changelog: takahirom/roborazzi@1.29.0...1.30.0
Full Changelog: takahirom/roborazzi@1.30.0...1.30.1
v1.30.0
Compare Source
Please refer to version 1.30.1
v1.29.0
Compare Source
Bug Fixes
We introduced an image diff percentage in the report. However, when the screenshot's image size changes, there was an issue causing Roborazzi to crash. We have added a test for image size changes and fixed this problem. Thank you for reporting this. @Daiji256
Breaking Change
We are migrating our codebase to Kotlin Multiplatform (KMP). Roborazzi uses dropbox/differ to calculate image diffs. Thanks to @eyedol 's contribution, differ now supports KMP for iOS, so we updated dropbox/differ. Some KMP migration is still needed for iOS support.
What's Changed
Full Changelog: takahirom/roborazzi@1.28.0...1.29.0
v1.28.0
Compare Source
Breaking changes
Now we are using
gradlePropertiesPrefixedBy
to support Gradle Isolated Projects in the Roborazzi Gradle Plugin. This API requires Gradle 8.0. Gradle 8.0 was released early last year, and most projects I know use 8.0 or higher, so Roborazzi is going to use this API. If anyone can't use this, please let me know.@trevjonez, thank you for telling me what we need to do to support this.
Currently, we aren't able to ensure compatibility with Gradle Isolated Projects, but this could bring some progress.
Adapting to the new ComposablePreviewScanner version
We are using ComposablePreviewScanner for Compose Preview Support. The ComposablePreviewScanner is now on Maven Central 🎉 and the group name of the libraries has changed. We have adapted to the new version and don't show errors when not using Jitpack and using the new packages.
What's Changed
Full Changelog: takahirom/roborazzi@1.27.0...1.28.0
v1.27.0
Compare Source
Bugfix for Compose Preview Support
As Compose Preview Support don't automatically add dependencies to maintain a single source of truth for user projects, they should show warnings when the required dependencies are missing. However, the warnings were not shown, so I fixed this issue. Thanks for reporting this! @kktaro
Diff Percentage to Report File
@vladcudoidem added the diff percentage to report files. You can use it in your CI workflow or project statistics.
The Roborazzi AI feature prototype is ongoing. 🤖
This version does not include it, but I've implemented a prototype for using AI for assertions. If you are interested, please check it out and leave feedback.
https://github.com/takahirom/roborazzi/pull/491
What's Changed
New Contributors
Full Changelog: takahirom/roborazzi@1.26.0...1.27.0
v1.26.0
Compare Source
Bugfix for iOS Compose Roborazzi
The iOS Compose Roborazzi has broken. The reason is that GitHub's macos-latest has switched to an ARM-based CPU, and our tests have been running X64Test. We couldn't check the status of iOS Roborazzi. We have fixed this bug that prevented us from writing the test result JSON. Special thanks to @eyedol for the prompt fix!
What's Changed
Full Changelog: takahirom/roborazzi@1.25.0...1.26.0
v1.25.0
Compare Source
New Experimental Gradle Task:
clear
The Roborazzi Gradle Plugin saves image caches in
build/intermediates/roborazzi
. When users remove images inbuild/outputs/roborazzi
and rerun the tests, it doesn't work as expected. To address this, we've added a Gradle taskclearRoborazziDebug
to remove all images.I'm gathering feedback about this task in #452. Please let me know if this causes any issues in your workflow. I'm aware that there are many different ways to use Roborazzi, and I'd like to improve your project workflow.
What's Changed
Full Changelog: takahirom/roborazzi@1.24.0...1.25.0
v1.24.0
Compare Source
New feature: Support for includePrivatePreviews in Compose Preview Support
Compose Preview Support, initially released in version 1.22.0, now includes the
includePrivatePreviews
option. This feature allows you to include private previews in your Compose Preview Support setup. You can enable this by settingincludePrivatePreviews
inroborazzi.generateComposePreviewRobolectricTests.includePrivatePreviews
. Thank you for submitting this feature request, @yuchan2215 !New feature: JUnit rule support in ComposePreviewTester
We've enhanced ComposePreviewTester to support JUnit rules. Previously, ComposePreviewTester lacked lifecycle hooks, which made certain scenarios challenging to handle. Now, you can pass your own Test rules, including your Compose Test Rule, and use them in tests. For a sample implementation, check out this integration test.
Breaking changes for users of the
ComposePreviewTester
interfaceAs we continue to improve Compose Preview Support, we've made some changes to the
ComposePreviewTester
interface. These changes introduce a breaking change for current users.ComposePreviewTester is an interface for modifying the behavior of Compose Preview Support. Previously, the API was prone to breaking changes with each new option added. We've addressed this issue by introducing a new
options()
function. However, this necessitates a change in how you use the interface.Old interface:
New interface (Packages can now be accessed via
options().scanOptions.packages
):Acknowledgments
We'd like to extend our sincere thanks to @yschimke and @sergio-sastre for their valuable design reviews and insightful feedback, which greatly contributed to the improvements in this release.
What's Changed
Full Changelog: takahirom/roborazzi@1.23.0...1.24.0
v1.23.0
Compare Source
Breaking Changes to
roborazzi.generateComposePreviewRobolectricTests.customTestQualifiedClassName
Gradle ExtensionWe released
roborazzi.generateComposePreviewRobolectricTests.customTestQualifiedClassName
in the previous release1.22.0
, allowing customization of preview test behavior. We have since discovered that the interface of RobolectricPreviewTest cannot adapt to Compose Multiplatform Preview because RobolectricPreviewTest usesAndroidPreviewInfo
from ComposablePreviewScanner, which represents Android Compose Preview. To address this, we have added a generic parameter to handle the annotation and renamed RobolectricPreviewTest to ComposePreviewTester.The Gradle extension property has been renamed:
roborazzi.generateComposePreviewRobolectricTests.customTestQualifiedClassName
->roborazzi.generateComposePreviewRobolectricTests.testerQualifiedClassName
Old interface:
New interface:
What's Changed
Full Changelog: takahirom/roborazzi@1.22.2...1.23.0
v1.22.2
Compare Source
Notice
RobolectricPreviewTest and roborazzi.generateComposePreviewRobolectricTests.customTestQualifiedClassName are used for customizing Experimental Compose Preview Support. However, the name and class signature of RobolectricPreviewTest will be changed in a future release(not in 1.22.2) to support the Compose Multiplatform Preview Annotation.
Bug fixes
We didn't have integration tests for Experimental Compose Preview Support, so we added them. In KMP projects, we used to check only
testImplementation
(androidUnitTest.dependencies.implementation is used for KMP Android Unit tests), and the verification for generateComposePreviewRobolectricTests{} was failing. Therefore, we have added integration tests and fixed the behavior for KMP projects.What's Changed
Full Changelog: takahirom/roborazzi@1.22.1...1.22.2
v1.22.1
Compare Source
Bug fixes
We've released Experimental Compose Preview Support in 1.22.0. In this release, we are going to include a bug fix for it.
The strategy of
generateComposePreviewRobolectricTests{}
is not to modify settings automatically, but to verify that the user settings are correct. This allows our settings to be the single source of truth. However, the assertion had some bugs, so I fixed them.What's Changed
Full Changelog: takahirom/roborazzi@1.22.0...1.22.1
v1.22.0
Compare Source
Experimental Compose Preview Support 🚀
We're excited to announce the experimental release of Compose Preview Support for Roborazzi, a powerful new feature that streamlines the process of generating screenshot tests for Jetpack Compose Previews.
Key Features
How to Use
To enable Compose Preview screenshot test generation, add the following to your
build.gradle.kts
:After configuration, run the
recordRoborazziDebug
task to generate screenshots using the newly created tests.Customization Options
Customize your setup with options like:
Manual Integration
For manual integration, add the following dependency:
testImplementation("io.github.takahirom.roborazzi:roborazzi-compose-preview-scanner-support:[version]")
Then use the
ComposablePreview<AndroidPreviewInfo>.captureRoboImage()
function in your tests. Note thatComposablePreview
is a class provided by the ComposablePreviewScanner library, which Roborazzi utilizes for this feature.This approach allows for more fine-grained control over the screenshot capture process for Compose Previews.
Acknowledgements
Special thanks to @yschimke for the initial proposal, and to @sergio-sastre and @yschimke for their valuable design and code reviews.
For more detailed information on setup and usage, please visit our [documentation](https://takah
Configuration
📅 Schedule: Branch creation - "* 0-3 * * *" in timezone Asia/Seoul, 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 was generated by Mend Renovate. View the repository job log.