Basically quibblr creates screenshots of defined url sets and stores them in versions.
These versions can be compared graphically to find differences between the versions.
There are two different situations:
If quibblr finds the button, and no other differences, your new feature is good to go.
If no differences are found by quibblr, you know the update, did not influence your frontend.
As you see you can have different assumptions, when changing some parts of a website.
Quibblr ensures that there are no other changes on your website except the ones you assume.
Short: Yes that is possible.
Lets assume you are doing an update of your cms, that can not be done on the live site. In this case you would need to clone the live site. So you end up with two different servers example.com (Live) and staging.example.com (Staging/Update). On the staging server you do the update, but after you are finished, how can you ensure the everything works like it does on the live site? Quibblr gives you solutions for that:
When a version is created, quibblr will create a graphical capture for every url specified in the project.
A compare is a graphical comparison between two versions.
So lets assume we have two versions A and B, with the same url set ('/','login','news'). Quibblr will now compare the graphical captures between these version.The matching takes place following the url set. So A '/' will be compared with B '/' and so on.
Capture presets are resolutions that are available for capturing a website e.g. 1024x768.
Every project needs to have a couple of urls. There are four ways of adding urls to your project:
You can create a sitemap on your own and simply copy paste the xml to your project.
If your webserver already provides a sitemap xml you can add that url to your project.
You can crawl your complete site. We will not include links to documents or images.
Just add your urls manually one by one.