Buddy Works
The agentic cloud. Compute, storage & delivery in one place.
Start new thread

Buddy Visual Tests - Every UI change, reviewed before merge

by
•
Not only can AI agents build your UI, they can now test what it actually looks like. Buddy Visual Tests captures every UI change, compares it pixel by pixel with an approved baseline, and brings visual regression testing straight into your delivery flow. With CLI, MCP and Skills support, agents can spot visual bugs, fix them, rerun tests, and hand over intentional changes for human approval.

Add a comment

Replies

Best
Maker
📌
Hi Product Hunt! We created Visual Tests because UI changes are getting faster and more frequent, especially with AI coding agents in the loop, but visual QA is still often manual, inconsistent, or happens too late. Visual Tests gives you a clear before-and-after of every UI change, with pixel-level comparisons, baselines, and review built directly into the delivery flow. What gets especially interesting is that the same workflow is available to AI agents through CLI, MCP, and Skills. That means visual checks can become part of the coding loop itself: an agent can make a change, run the tests, inspect the result, and react before the change reaches production. How are you handling visual QA in your team today? And do you think you could rely on agents to handle part of it?
Maker

Hi, 

Head of the Buddy frontend team here. Most of our frontend workflow already exists in Buddy: building Storybook, unit and e2e tests, preview environments (sandboxes) and automation. The only thing we had to do externally was visual regression. 

Now every change runs against approved baselines and visual diffs across the component library get flagged automatically. Each run also publishes a hosted Storybook preview for the branch, which is handy when a diff needs a second pair of eyes.

Hi,

Head of the Buddy QA team here. We’re running a couple thousand Playwright tests that cover pretty much the entire platform.

Adding Visual Tests on top of that gives us another layer of confidence. Playwright tells us whether everything works as expected, while Visual Tests help us catch layout shifts, styling issues, and other visual regressions that can still slip through a passing test suite.

For us, it fits naturally into the QA process we already had in place rather than replacing anything.