-
Notifications
You must be signed in to change notification settings - Fork 17
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
Updates dropshots to always write reference image. #64
Conversation
This seems weird, but matches the behavior of the connected instrument test task, so 🤷.
when the assertion is done, could we record the screenshot simultaneously? It would prevent us from re-running the test if we agree with the changes |
That's what I'm working on now with this change. Sorry for the thrash in this PR, but validating the GHA integration is hard to do without a PR. |
This updates the behavior of the plugin to remove the need for the
dropshots.record
property, which broke configuration caching. With that being deprecated, the new way to record new reference screenshots is by using therecordDebugScreenshots
gradle task.Since switching to a task means we won't be compiling a new APK for the test, the updated behavior is to use a marker file written to the emulator to disable assertion failures when recording new screenshots.