Dev / DevOps

For a normal manual visual regression process, we would usually tend to use the default way of fetching URLs, by crawling the site and letting this be our URLs monitor list. Using the default URL crawls is definitely convenient but it can also be a double edge sword. URL crawls sometimes can lead us to have 30~40 URLs to monitor per site, this might be viable if you are only monitoring 1 site but what if you have to do visual regression tests on multiple sites?
The time spent reviewing any true or false triggers can quickly turn into a time sink and you can be spending days reviewing every site you have. 
In the presentation, we can look at our visual regression testing workflow that involves using Diffy as a visual regression tool differently to only monitor targeted URLs which could possibly save you hours during your manual visual regression testing.
Using specific URLs to monitor a specific purpose might be the angle that you need to save time.