ScreenshotTestingDemo
A demo PoC for usage of screenshot testing as a regression QA tool
The proof of concept
In the master branch, we have a simple ViewController with a fake login screen. This screen has been recorded by iOSSnapshotTestCase on the following path
In PR #3, we have a CI failure. This is caused by iOSSnapshotTestCase detecting a change in the new screenshot. This is done on purpose to showcase the screenshot testing feature. The only way to make the CI pass at this point is to either fix the change, or re-record this screen and commit the new screenshot file.
Validating on development machines
When running the unit tests in the failure branch, iOSSnapshotTestCase generates an image file with the visual diff between the two:
The medium gray background indicates no change between the versions. Notice the gray line towards the upper middle part of the screenshot. This is where the library detected changes. This indicates to us that there is a problem with the password field. It’s width has changed.
The reference, failed and diff images are saved in the FailureDiffs folder. These shouldn’t be commited to the repo as they are debugging tools for developers and serve no purpose on the CI.
About the library
iOSSnapshotTestCase works by comparing a unit test screenshot to a reference image stored in the repo.
To setup a new screenshot testing case:
- Create a unit test file that inherits from
FBSnapshotTestCase. This unit test should be able to create and load the view to test - To enable recording of new screenshots, we need to set
self.recordModeto true in thesetUpmethod - In the unit test, validate the view by calling
FBSnapshotVerifyView - Run the test so that the reference screenshot is generated and saved
- Set
self.recordModeto false before pushing
See iOSSnapshotTestCase for more details on usage
