IssueTracker

It looks like it is because of anti-aliasing differences between your host and Github action runner, we are seeing the same between MacOS dev machines and Bitrise runner causing all screenshot tests to fail. This could be resolved by this Feature Request: https://issuetracker.google.com/issues/342461560 allowing for some slight pixel variation due to different platform implementations

I understand the concern about maintaining the integrity of screenshot testing. However, it's important to note that anti-aliasing like this is typically managed at the OS graphics layer. I think achieving consistent anti-aliasing across all environments and platforms might not be feasible. Instead, allowing for slight pixel variations in screenshot testing might be a more practical approach given these inherent differences. One that other screenshot testing platforms have also used. This way, we can accommodate the natural variations while still effectively validating the visual aspects of our applications. If it's configurable, we could make the default threshold no differences and for people who do all their testing on a single platform that would likely be sufficient. This just opens up options for everyone else.

We've used the imageDifferenceThreshold settings in our build.gradle file and it works fine. But sometimes there are bigger differences between platform results, as you can see in the screenshot above.

I'm not sure that these settings will fix the anti-aliasing issues :/

Do we have any news? Is the compose team working on any definitive solution?

Same issue with Bitrise. Would love to see an update on this one :D

Do we have any news?