Screenshot comparison (Visual regression) - assertion step
We plan to add a separate step for screenshot comparison. The first execution will save a screenshot as a baseline, and then every next execution will be compared to this baseline screenshot. If the new screenshot is different from the baseline, the test will fail.
Possibly, this step should also have an option to
exclude some random elements from the DOM before taking a screenshot
option to decide how this comparison should be done (pixel perfect or percentage)
option to verify screenshot only for specific element on the page (given selector)
Any other ideas around this feature are more than welcome.
Log in to comment and vote
Comments26
Apr 30
PinnedFinally, Visual Regression has arrived! 🥳
This is the first implementation, and the documentation will soon be upgraded with some screenshots.
https://docs.bugbug.io/visual-regression/how-does-it-work
Please feel free to check it out and give us your feedback. The feature is available on paid plans (PRO & BUSINESS).
Official information about this feature will be sent in the newsletter.
Jan 28
PinnedWork on this feature is at an advanced stage.
Rav Banaag
Feb 5, 2024
Probably add console log and network log would be nice to debug it.
Kalai
Mar 7, 2024
This is for me the only missing feature on bugbug. Hopefully it will be delivered soon.
Paweł Bylina
Mar 7, 2024
@Kalai great to hear! ;) This will be scheduled soo.
Kalai
Jun 5, 2024
Is there some light at the end of this tunnel?
Paweł Bylina
Jun 11, 2024
Probably in Q3/Q4 this year.
Kalai
Apr 3, 2025
We are at Q2 a year after. Any updates?
Paweł Bylina
Apr 7, 2025
There is currently no ETA :( We are currently prioritising feature requests from paid customers.
Yotam Faraggi
Nov 5, 2024
This would be awesome!!! Adding screenshot comparison as an assertion step would make it so much easier to catch CSS issues and those tricky, unexpected JavaScript bugs. Plus, having options like excluding random elements, choosing comparison accuracy (pixel vs. percentage), and targeting specific elements would make it super flexible.
Paweł Bylina
Nov 7, 2024
I absolutely agree. We plan to start working on this in Q1 2025.
Prolorus
Nov 27, 2024
Yes please, this is an essential feature that is missing when I compare with other automated testing platforms. Being able to exclude specific elements before the screenshot is also something that is common across the other platforms.
Paweł Bylina
Nov 27, 2024
Thanks for this comment!
Prolorus
Dec 12, 2024
Just re-iterating after reviewing available testing products that being able to capture just a portion of the screen or a certain element while also being able to pre-exclude certain elements before the screenshot would make this very useful for us! And being able to do multiple screenshot assertions throughout a single test.
The other options on the market do some of this but not all….
Paweł Bylina
Dec 12, 2024
We plan to implement them all! The "how" discussion has started internally and I think we have some exciting improvements compared to what the market offers. Thanks for your research ;)
Anton Eremin
Jan 24, 2025
I wanted to echo the value of this feature. For our use case, we just want to use screenshots to pass these to LLMs and compare baseline to the current screenshot and parse analysis - e.g. “these are identical” or “the analysis is close to what it should be”, etc.
Paweł Bylina
Jan 29, 2025
Thanks for your feedback. We plan to have this feature builtin.
Ken Lyle
Oct 22, 2025
I upvoted, but would encourage BugBug not to focus on this. It seems to me a perfect situation for a partnership with some other company which specializes in such things.
Software architecture works best with loosely coupled best of breed systems in my experience. Monolithic went out with “We’re an IBM Shop”, or “We only run Microsoft products”…says nobody in 2025.