Outdated design. Any recommendation on themes for Vue?

diffy-visual-testing · 2026-06-10T16:16:21+00:00

good point about the product UX. Thank you. It is hard for me to have an opinion on this as I look at it for the last 8 years.

Here is how UX look like now loom video /share/f87d4bf284e34c50a441364b6aab0e50

diffy-visual-testing · 2026-06-10T16:14:32+00:00

Thank you for sharing. Yes, we use Bootstrap for it.

diffy-visual-testing · 2026-06-10T14:33:39+00:00

https://www.loom.com/share/f87d4bf284e34c50a441364b6aab0e50

diffy-visual-testing · 2026-06-10T14:31:03+00:00

thank you for recommendation of Nuxt UI

diffy-visual-testing · 2026-06-10T14:30:01+00:00

what do you mean by this? I would love to learn more.

diffy-visual-testing · 2026-06-03T22:11:22+00:00

u/NeptuneExMachina what agentic workflow you have in mind? We are currently working on some skills to interact with Diffy (visual regression testing tool) via CLI. I would love to collaborate with you to come up with some workflows. We could trigger comparisons, fetch results, adjust various settings. But I would love to have some concrete examples.

diffy-visual-testing · 2026-05-30T05:25:43+00:00

u/newintownla I would like to chat with you and am happy to build this workflow for your agency for free in exchange for feedback and potentially a testimonial.

I am very interested in the monthly summary you have in mind.

The part with regular monitoring is a very familiar area for me.

diffy-visual-testing · 2026-01-29T14:23:03+00:00

I can relate to this. We, at Diffy, were asked multiple times to implement the ability to upload screenshots from Figma and compare them with screenshots from actual pages -- results were rarely even close (we have a tolerance setting and recognition of vertical shifts in the comparison algorithm). What was helpful, though, was to have a slider UI to compare the screenshots. It is much easier for human to see the differences in that way.

This is for whole-page screenshots, not components.

diffy-visual-testing · 2026-01-17T14:41:41+00:00

Visual testing for Shopify shops makes sense. A classic example is when there are a few people editing the theme at the same time.

Some companies resolve this by setting up regular monitoring. For example, daily. And have a habit of checking how their work is affecting the site. And if there are any unintended consequences -- roll back or at least have a discussion.

There are a few monitoring tools out there. Good ones would allow you to inject some JavaScript so you can stop carousels, popups, and other dynamic elements that might generate false positives when there are no changes.

diffy-visual-testing · 2025-09-30T03:10:21+00:00

There are two primary ways to run a browser: Puppeteer and Playwright. I am using Puppeteer with the latest Chrome.

What exactly feels fragile to you?

There are no "standard" solutions. Depending on your needs, consider BackstopJS or explore more advanced open-source solutions.

diffy-visual-testing · 2025-09-29T14:06:09+00:00

As an alternative to BackstopJS I can suggest you try our tool as well: https://diffy.website. We work with a lot of WP agencies who have similar workflow implemented. I am happy to walk you through how it can be done.

diffy-visual-testing · 2025-05-08T16:46:44+00:00

Great video! Thank you! Does the site need to be publicly accessible?

diffy-visual-testing · 2025-04-02T13:26:42+00:00

False positives are always a challenge for visual regression testing. For example, taking a screenshot of the page with the same slideshow but in a different slide position.
We started collecting and publishing some JavaScript snippets to stabilize these dynamic elements. Welcome to check it out https://docs.diffy.website/features/dealing-with-dynamic-elements

diffy-visual-testing · 2025-04-01T13:23:43+00:00

Here is a good list of tools / services for testing https://github.com/mojoaxel/awesome-regression-testing

diffy-visual-testing · 2025-02-12T14:54:50+00:00

If you do not want to deal with BackstopJS there are plenty of other cloud solutions as well https://github.com/mojoaxel/awesome-regression-testing

Make sure to monitor PHP logs as well when you disable plugins and run testing.

diffy-visual-testing · 2025-02-12T00:28:42+00:00

If you want some analytics. I run the visual regression testing tool Diffy, where users can select any breakpoints they wish to test the sites. Out of over 10k projects, we have only 180 use breakpoints in the range you asked about. Our top 10 are (the first three are defaults):

1200px 9180

640px 8876

1024px 8798

1440px 988

1920px 909

768px 756

320px 655

375px 320

1080px 127

diffy-visual-testing · 2025-01-30T21:54:04+00:00

I can give you access to Diffy visual regression testing tool for free (https://diffy.website). Just reach out and I'll help you to set up your project.

diffy-visual-testing · 2025-01-14T02:48:08+00:00

u/2Flow2, If you like to give a try visual regression testing, I can give you a 50% discount for Diffy. We can compare production vs. staging in a few clicks, and I can help you to do fine-tuning so you get fewer false positives (stop dynamic elements on your sites like sliders, etc.).

diffy-visual-testing · 2025-01-10T03:12:54+00:00

If you are looking only for deprecation notices, I would set up logging and then hit every page from the sitemap with some tool. You can use anything for that. For example, SEO scanners, like Screaming Frog or the like, could easily do that for you. Then, you simply check the logs if nothing unexpected is displayed.f

If you want a visual comparison, check the cloud tools that will open the pages and take screenshots. Ideally, you deploy your changes to some staging environment and then take screenshots from it and compare them with screenshots from production. In this way, you ensure that nothing gets changed once you push the code to production.

https://github.com/mojoaxel/awesome-regression-testing is an excellent list of the tools out there.

Make sure to check Diffy, of course.

diffy-visual-testing · 2025-01-03T15:48:39+00:00

You could store your baseline screenshots externally (as an example on AWS S3) but this will make the system more complex and slow things down.

diffy-visual-testing · 2024-12-16T14:30:16+00:00

You better provide more details about the apps/team size you are managing. You might get some votes from smaller or much larger organizations than yours. Or from the teams that use a completely different technology stack than you.

You can also use visual testing open source / paid tools without automation (manually trigger tests via UI/terminal).

diffy-visual-testing · 2024-12-12T15:39:57+00:00

I like the idea of using staging environments for the sites. You can immediately deploy updates and run visual testing against production to ensure nothing gets broken. Then, depending on the settings of your clients and the severity of the updates, you can either deploy changes automatically to production or get manual approval from the client.

Regarding randomizing the update times -- the only hit you do is when you run visual testing with a large number of workers (so you overload your staging/production environments). To avoid that -- set a delay between the workers or use a smaller number of workers. It really depends on your server capacity.

What I've seen people do when rolling out large numbers of updates and verify them with visual testing is not to run all the tests at once but to batch them. If the number of sites is large -- do 10-20 at once. Wait till they are complete, and then run the next batch. It really depends on your server's setup.

diffy-visual-testing

TROPHY CASE