-
Notifications
You must be signed in to change notification settings - Fork 215
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
Failure image generated despite no change of code and their diff incorrectly rendered #99
Comments
There should not have been any changes that would cause a regression like this. Are you saying these snapshots worked correctly on a previous version of iOSSnapshotTestCase and 6.1.0? If you are upgrading to a new iOS SDK version these sort of blips are typically expected because of the major changes that Apple typically makes to UIKit. |
Same issue here. I am using :
As soon as I turn off
Through testing different cases I noticed that if |
@zeksa90 that is a different bug that is potentially fixed by #100 and is in the v6.2.0 release. You can see with your difference image that it recorded at 3x but then compared at 1x. It is a shortcoming of UIKit that if an image does not end with the appropriate @ suffix it assumes it to be 1x. The PR that fixed it makes iOSSnapshotTestCase use the actual pixel size rather than the logical device size. |
@imaizume does v6.2.0 fix your issue? |
Hi, I'd like to report wired behavior.
I tried to take snapshot of root view for a simple ViewController.
After recorded its reference image successfully, turned
recordMode
into false and found the test failed.Without any code nor visual changes to the ViewController, diff is rendered as below.
With iPhone Xs simulator, failure image slightly changes from its reference image (of course with no change in code nor storyboard) and diff is incorrectly rendered too.
The ViewController
storyboard.instantiateInitialViewController()
)viewDidLoad
I couldn't make sense of it and hope this to be resolved.
The text was updated successfully, but these errors were encountered: