Replies: 1 comment 2 replies
-
If you're trying to avoid manually recording screenshots you could use a third-party service to notify you when screenshots change in CI. I've built screenshotbot.io (open source at https://github.com/screenshotbot/screenshotbot-oss), but there's also another similar open source tool built by Workday https://github.com/workday/vizzy. With these you'll just always be running your tests in record mode, add your snapshots to |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First of all thanks for the fantastic snapshotting package, it's a joy to use and work with.
At my place of work we've recently gotten used to using a local override of the
assertSnapshot
function that usesverifySnapshot
to check if a snapshot has changed and if so, automatically copying the new snapshot to the correct directory to overwrite the old one and then fail the test. That way a developer doesn't need to manually rerecord updated snapshots but already sees a new one in their git diff which they can either accept as a known change or discard in case it actually is wrong and needs code changes to fix.So far this feels like a nice improvement in the typical workflow. Is something like this already possible but we just missed it entirely? Or could this be an improvement to the existing API or swift-snapshot-testing?
Beta Was this translation helpful? Give feedback.
All reactions