Users should be able to define a manualScale instead of being locked into the mainScreen.scale - #15
Users should be able to define a manualScale instead of being locked into the mainScreen.scale#15regnerjr wants to merge 3 commits into
manualScale instead of being locked into the mainScreen.scale#15Conversation
* Manual scale wasn't propagated properly to image capture and reference image selection methods
|
|
This better reflects the duality between it an `UIScreen.scale` which has type `CGFloat`
|
@regnerjr of course no problem, go ahead 👍 |
|
I'll take a look at this soon. |
|
Is this resolved here? |
|
@alanzeino |
|
Thanks for the support on this Alan. 👍 Really glad you are supporting this project. I'm thinking perhaps a better approach (instead of having a fixed size window and trying to do all of our snapshotting in there) will be to do snapshots for all devices we support. Glad we've got a fix for that issue sorted out (each just needs it's own build folder) #37 Cheers. Keep up the good work. |
|
It seems the capability for using |
What did you see when debugging the manualScale? |
In order to stay flexible, users of this library "need" to upload two version of there reference images to keep tests passing on various environments (Other Developers, CI, etc)
This proposal would not lock users in to always using the "one true simulator" to run their tests on.
We've recently adopted Snapshot testing at my shop and I don't really want to be the the code review czar ensuring every new PR which adds a snapshot has one at
@2xand@3x. Other cancers are the size of our git repo growing over time to support 2 screenshots for each new test.This work was originally proposed by @djrtl as facebookarchive/ios-snapshot-test-case#166
Thanks for doing the original implementation @djrtl, I hope I did not overstep by re-opening this here now that this lib is under new ownership.