You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Roborazzi processes a @Preview (using the Compose Preview support) containing an indeterminate LinearProgressIndicator (during recordRoborazziDebug, verifyRoborazziDebug, etc.) it stalls for a good 4 minutes or more (whereas all other @Preview-based tests are quick). We assume that the delay has to do with the ProgressIndicator animation so we are skipping those @previews using a custom ComposePreviewTester for now. However, is there a strategy for dealing with such tests that contain animations?
The text was updated successfully, but these errors were encountered:
Thanks.
One thing I can recommend is adding the DelayedPreview annotation. With this annotation, you can set mainClock.autoAdvance = false and then use mainClock.advanceTimeBy(delay). This should help the test finish quickly.
The information is in Japanese, but you can refer to the code.
When Roborazzi processes a @Preview (using the Compose Preview support) containing an indeterminate LinearProgressIndicator (during recordRoborazziDebug, verifyRoborazziDebug, etc.) it stalls for a good 4 minutes or more (whereas all other @Preview-based tests are quick). We assume that the delay has to do with the ProgressIndicator animation so we are skipping those @previews using a custom ComposePreviewTester for now. However, is there a strategy for dealing with such tests that contain animations?
The text was updated successfully, but these errors were encountered: