Skip to content

Diffy API integration and workflow automation

Diffy is a visual regression testing tool that compares screenshots of your website or application across different environments, browsers, or time periods...

What we connect Diffy toWe integrate and automate Diffy alongside AMQP Sender, Transifex, Botifier, LaGrowthMachine, Invoiced, Datarobot and hundreds of other systems.osher.com.auDiffyintegrated & automatedAMQP SenderTransifexBotifierLaGrowthMachineInvoicedDatarobot
Diffy

What you can automate with Diffy

Diffy is a visual regression testing tool that compares screenshots of your website or application across different environments, browsers, or time periods to detect unintended visual changes. It captures baseline screenshots and compares them against new screenshots pixel by pixel, highlighting differences so your QA team can quickly spot layout shifts, broken styles, missing elements, or other visual defects before they reach production. Code changes that look harmless in a pull request can cause unexpected visual side effects — a CSS update that breaks spacing on a different page, a component library upgrade that shifts button alignment, or a content change that causes text overflow. Manual visual checking is slow and unreliable, especially across responsive breakpoints and multiple page templates. Diffy automates this comparison at scale, catching issues that human reviewers would likely miss. Osher Digital builds and maintains web applications for Australian businesses, and visual quality is a non-negotiable part of delivery. Our custom AI development team integrates testing tools like Diffy into CI/CD pipelines, so visual regressions are caught automatically before deployments go live. For organisations running content-heavy websites where template changes can affect hundreds of pages, our automated data processing services can set up batch screenshot comparison workflows that cover your entire site. If your team has experienced the frustration of deploying a change that looked fine in development but broke the layout on a page nobody thought to check, visual regression testing removes that blind spot. Explore our business automation services to see how automated testing fits into a broader quality assurance strategy.

Diffy FAQs

Frequently Asked Questions

Common questions about how Diffy consultants can help with integration and implementation

Visual regression testing compares screenshots of a website or application before and after a change to detect unintended visual differences. Unlike functional testing that checks whether features work correctly, visual regression testing checks whether the interface still looks correct — catching layout shifts, styling breaks, and rendering issues.

Diffy captures screenshots of specified pages and compares them pixel by pixel against baseline images. It highlights areas where differences are detected, producing a visual diff that makes it easy to see exactly what changed. You can configure sensitivity thresholds to ignore minor rendering variations like anti-aliasing differences.

Yes. Diffy can capture screenshots at different viewport widths to test responsive layouts, and can render pages in different browsers to catch cross-browser rendering inconsistencies. This ensures your visual testing covers the range of devices and browsers your users actually use.

Diffy can be triggered as part of your CI/CD pipeline, running automatically on pull requests or staging deployments. When visual differences are detected, the team is alerted to review the changes before merging or deploying, preventing visual regressions from reaching production.

Diffy detects layout shifts, broken CSS styles, missing images or icons, font rendering changes, colour differences, misaligned elements, text overflow, and unintended content changes. Any visual change that produces a pixel-level difference from the baseline will be flagged for review.

When a visual change is intentional — such as a redesign or content update — you update the baseline screenshots to reflect the new expected appearance. Diffy then uses these updated baselines for future comparisons, so intentional changes do not continue to trigger false positives.

How it works

Implementing Diffy

Step 1

Define Pages and Breakpoints to Test

Identify the key pages, templates, and responsive breakpoints your visual testing should cover. Prioritise high-traffic pages, pages with complex layouts, and templates that are reused across many URLs — these are where visual regressions have the highest impact.

Step 2

Capture Baseline Screenshots

Run Diffy against your production or approved staging environment to capture baseline screenshots for every page and breakpoint combination you have defined. These baselines represent the expected visual state that future changes will be compared against.

Step 3

Configure Your Comparison Settings

Set the pixel-level sensitivity threshold for comparisons. A too-tight threshold flags minor rendering variations as issues, while a too-loose threshold may miss genuine regressions. Adjust based on your quality requirements and the level of visual precision your design demands.

Step 4

Integrate with Your CI/CD Pipeline

Connect Diffy to your deployment or pull request workflow so that visual comparisons run automatically when code changes are proposed. Configure the integration to block merges or deployments when significant visual differences are detected, requiring team review before proceeding.

Step 5

Review Visual Diffs and Resolve Issues

When Diffy flags visual differences, review the highlighted changes to determine whether they are intentional design updates or unintended regressions. Fix any regressions before merging the code change, and approve intentional changes to update the baseline.

Step 6

Maintain and Expand Test Coverage

As your site grows, add new pages and templates to your Diffy configuration. Regularly review and update baselines after approved design changes. Monitor the overall trend of visual regressions to identify patterns — such as a particular component that frequently causes layout issues.

Works well with Diffy

Other tools we connect and automate alongside Diffy.

Get in touch

Ready to automate Diffy?

Tell us what you want Diffy to talk to and we’ll map out the build, the cost and the payback.

Diffy enquiry

Name(Required)

Australian-hostedPrivacy Act compliantNDAs standard