3 ms·
It writes a .huxley dir that contains screenshots and a log of user actions. It can replay these user actions programmatically and if the screen shots have chan
by peterhunt 13y ago
It writes a .huxley dir that contains screenshots and a log of user actions. It can replay these user actions programmatically and if the screen shots have changed it will save new ones to disk. You can use a tool like Kaleidoscope to compare the old ones with the new ones (we use git to keep the old ones around).
When you commit, the tests will be updated and the new screenshots will be part of the code review.
Additionally, you can run it in continuous integration mode which will break the build if screenshots are out of date.
- abritishguy 13y agoJust to clarify, if I want to run this as part of travis then I should have the screenshots under source control and when I intentionally change the UI I should run it locally and push the new screenshot as part of the commit but when I don't intend to change the UI it will fail the build if something changes.
- peterhunt 13y agoYep!
- faramarz 13y agoThat's quite amazing! Thanks for the write up! Will look into it