Visual regression: an unintended change in the appearance of a user interface (layout, colors, typography, spacing, alignment) introduced by a code change, a dependency update, or a configuration change, and detectable only by visually comparing two states of the interface.
Here is a truth many teams using Cypress would rather ignore: your Cypress test suite, however complete, is structurally blind to an entire category of bugs. Visual regressions slip through your assertions like water through a sieve, not because your tests are badly written, but because Cypress was simply not designed to detect them.
This is not a criticism of Cypress. It is an observation. And the difference between an observation and a criticism is that an observation calls for a solution, not a debate.
All our comparisons, based on verifiable criteria: Alternatives and comparisons.
Your Cypress suite confirms that everything works, not that everything looks right. Complete it with Delta-QA: your journeys recorded without code, a free account, and no credit card. Try Delta-QA for free →
Cypress: Excellent at What It Does, Absent Where Visuals Matter
Cypress revolutionized front-end testing when it arrived on the market. Running in the browser, automatic reloading, time-travel debugging, the intuitive API (all of this made end-to-end testing accessible to teams that considered Selenium a medieval instrument of torture). And in functional testing, Cypress remains a remarkable tool.
But ask yourself this: when did you last write a Cypress test that checks that your home page looks right? Not that a button exists. Not that a text is present. That it looks right: that the spacing is correct, that the colors are consistent, that the layout hasn't moved by a single pixel.
The answer, for the vast majority of teams, is "never". And it's not out of negligence. It's because Cypress doesn't compare images. Its own documentation says so as of 10/2026: the cy.screenshot() command captures an image but doesn't compare it; visual testing goes through plugins or third-party services.
Cypress's Blind Spot: No Native Visual Comparison
When you write cy.get('.button').should('be.visible'), you verify that the element exists in the DOM and isn't hidden by CSS. You don't verify that it has the right color. You don't verify that it's in the right place. You don't verify that its text is readable. You don't verify that it doesn't overlap another element.
A button can be "visible" in Cypress's sense (present in the DOM, display different from none, opacity greater than 0) and be completely unusable visually. White text on a white background. A size of 2 pixels by 2 pixels. Positioned 3,000 pixels to the right of the screen. Cypress will tell you everything is fine. Your user will tell you something else.
This is a fundamental blind spot, not a minor limitation. A significant share of the problems reported by users concerns display: an unreadable button, a shifted form, a block that overflows. And Cypress, in its native configuration, detects none of them.
Cypress's Visual Plugins: A Partial and Fragile Solution
Faced with this gap, the Cypress ecosystem has produced visual testing plugins. The best known rely on third-party services (Percy, Applitools, Happo) to capture and compare screenshots, or on cypress-image-snapshot for local comparison. If you want the detail of each option, our complete guide to adding visual testing to Cypress reviews these approaches and their real limits. It's a path that works, but with significant constraints.
Dependence on a third-party service. Every visual plugin for Cypress relies on an external platform. Your screenshots are sent to a provider's servers, compared there, and the results come back to you. That adds latency to your CI pipeline, a network dependency, and a license cost for the third-party service, on top of the cost of Cypress Cloud if you use it.
Configuration complexity. Adding a visual plugin to Cypress requires installing an npm package, configuring authentication with the third-party service, modifying your existing tests to add capture calls, managing API tokens, and training your team on the external platform. It's not insurmountable, but it's not the "works in 5 minutes" experience the marketing pages promise either.
Double maintenance. You end up maintaining two systems: your Cypress tests and the visual plugin's configuration. When Cypress updates, the plugin can break. When the third-party service changes its API, your tests can fail. When your team changes, new people have to be trained on two tools instead of one.
Limited coverage. A visual plugin integrated into Cypress captures screenshots while your functional tests run. Which means visual coverage depends on functional coverage. If you have no Cypress test for the "Terms and Conditions of Sale" page, you have no visual test for that page either. Your visual coverage is capped by your functional coverage, and the two have no reason to coincide.
Delta-QA: Visual Testing as a Standalone Discipline
Delta-QA starts from a different philosophy. Visual testing is not a feature grafted onto a functional testing tool. It is a discipline in its own right, with its own requirements, its own workflows, and its own users.
Independence from functional tests. Delta-QA records your journeys as you browse. You don't need a functional test as a vehicle to capture a page. Your visual coverage doesn't depend on your functional coverage: you can check dozens of pages without writing a single test.
Accessibility for non-developers. Who are the people best qualified to judge the visual quality of an interface? Designers. Manual QA testers. Product owners. And these people, in most organizations, can't write JavaScript. With Cypress + a visual plugin, they depend on a developer to configure, run, and interpret the tests. With Delta-QA, they are autonomous. It's a difference that changes a team's dynamics.
Native reference management. Delta-QA integrates a complete workflow: a report that names each changed element, judgment of each difference (intended or bug), change history. This workflow is designed for cross-functional teams, not for a solo developer who pushes and merges in the same morning.
The browser. Delta-QA replays your journeys in a real browser, Chromium today; Firefox and WebKit are planned. On the Cypress side, Chrome, Edge, and Firefox are supported, and WebKit remains experimental.
The Structural Problem with Plugins: The Law of Coupled Coverage
Let's come back to this point, because it deserves further development. When your visual test is coupled to your functional test (as is the case with Cypress's visual plugins), your visual coverage inherits all the limitations of your functional coverage.
You have a Cypress test for the checkout funnel? Visual coverage of the checkout funnel is ensured. You have no Cypress test for the FAQ page? No visual coverage of the FAQ page. Your Cypress test for the profile page covers the "logged-in user with a premium subscription" case? You have visual coverage for that case, but not for "logged-in user without a subscription" or "user whose subscription has expired".
Functional coverage and visual coverage follow different logics. In functional testing, you test journeys: sequences of actions and checks. In visual testing, you test states: snapshots of pages under given conditions. A 10-step functional journey may need only 2 visual checks (entry page and confirmation page). Conversely, a simple page with no complex functional logic (an "About" page) may require a visual check at 5 resolutions and 3 browsers.
Coupling the two forces one discipline to adopt the coverage of the other. It's like saying you will only visually inspect a factory room when a worker walks in to use a machine. On the days when nobody works in that room, water leaks go unnoticed.
Cypress Does This Better: Functional Testing
Let's acknowledge Cypress's strengths, because they are real and significant.
Developer experience. Cypress was designed by developers for developers. The debugging interface with time-travel, the execution speed, the fluent chained API (it's a pleasure to use). Delta-QA doesn't claim to offer that experience because it's not its playground.
Business logic verification. A payment funnel that computes taxes, shipping costs, and promo codes correctly: that's what Cypress checks. Not Delta-QA. Business logic is visually invisible until it produces a displayed result, and even then, verifying that "the displayed amount is correct" requires knowing the expected amount, which only a functional test can compute.
Network interception. Cypress can intercept HTTP requests, simulate server responses, and test error cases. It's a powerful front-end integration testing tool that goes well beyond simple interface checks.
A growing Cloud ecosystem. As of 10/2026, Cypress Cloud offers Test Replay to replay a failure, UI Coverage, Cypress Accessibility, AI-generated failure summaries, and the cy.prompt() command turns steps written in natural language into Cypress commands. None of this compares a page's appearance to a reference, but the tool is progressing fast.
Execution speed. Cypress's architecture, which runs tests in the same process as the application, delivers remarkable execution speed for functional tests. No network latency between the test and the application, no intermediate WebDriver protocol.
Your Cypress suite validates the logic, not the appearance. Close that gap with Delta-QA: no-code visual testing, a free account, and no credit card. Try Delta-QA for free →
Delta-QA Does This Better: Visual Testing
Fast coverage. Visually covering your main pages takes the time needed to browse them in Delta-QA. Getting the same coverage through a Cypress plugin would require writing a test for each page, managing baselines, and stabilizing captures. Days of work on one side, a few hours of browsing on the other.
The approval workflow. When Delta-QA detects a change, your designer can judge it directly in the interface. No need to go through a developer, no need to understand the Cypress report. The report speaks the language of the people who judge visual quality: which element changed, and how.
Fewer false positives. Visual plugins for Cypress often inherit the limitations of raw pixel-to-pixel comparison. A different font anti-aliasing between two runs? False positive. A text cursor caret appearing in a field? False positive. Delta-QA compares the elements of the page rather than its pixels: a rendering variation that changes neither the color, nor the size, nor the position of an element is not flagged.
Visual history. Delta-QA keeps the history of references and judged changes. You can trace a page's evolution across versions. With a local Cypress plugin, your baselines are files in Git (versioned, but with no interface to visualize their evolution).
The Typical Scenario: When the Cypress Plugin Is No Longer Enough
Let's imagine a common scenario. Your team has used Cypress for two years. You have 300 functional tests. Your coverage is good. Then one day, a CSS refactoring touches your design system. The --color-primary variable changes. The Cypress tests all pass, none of them checks colors. In production, 30 pages have an action button whose contrast has become too low to be readable. Support receives 15 tickets in two hours. The fix is deployed in an emergency.
After this incident, your tech lead decides to add a visual plugin to Cypress. The installation takes half a day. Setting up baselines for 50 critical pages takes a day. The first runs generate 47 false positives. Sorting through the false positives takes a day. Two weeks later, a developer updates Cypress and the plugin is no longer compatible. The visual suite is disabled "temporarily". Three months later, it's still disabled.
This scenario isn't invented: it's the composite story of dozens of conversations with QA teams. The fundamental problem isn't the plugin. It's that visual testing grafted onto a functional testing tool is never a priority. It's always "the extra thing" you do when you have time: that is, never.
Delta-QA avoids this trap because visual testing is the tool's reason for being, not an optional add-on. There is no functional suite that takes priority. There is no more urgent configuration to maintain. Visual testing is the priority, and the tool is built around that priority.
The Winning Combination: Cypress + Delta-QA
The position we defend is not "drop Cypress for Delta-QA". That would be absurd. Cypress is an excellent functional testing tool. Delta-QA is designed for UI regression testing. Combining the two gives QA coverage that neither can offer alone.
Cypress checks that your application works. User journeys, business logic, API integrations, error cases. It's the functional layer of your quality assurance.
Delta-QA checks that your application looks right. Colors, typography, spacing, layout. It's the visual layer of your quality assurance.
Each layer has its own rhythm. Cypress tests run in your CI/CD pipeline; Delta-QA scenarios are replayed on every version. Each looks at a different dimension of quality, with tools optimized for that dimension.
It's like having both an alarm system and surveillance cameras. The alarm detects intrusions (functional: someone came in who shouldn't have). The cameras show what is happening (visual: does everything look normal). Both together are more effective than either separately.
The "We Already Have Cypress, That's Enough" Argument
This is the most frequent objection. "We've already invested in Cypress, we're not going to add another tool." It's an understandable but fallacious argument. You already have a hammer, but that doesn't make every problem a nail.
If your application has a user interface (and if you're reading this article, it probably does), a significant part of the value your users perceive comes from how that interface looks. Not from the underlying business logic, however brilliant. A user doesn't see your microservices architecture. They see a blue button, an aligned form, consistent typography.
Not testing this dimension is betting that nobody will ever break your application's CSS. It's a bet you will lose. The question is not if, but when. And when it happens, the cost will be proportional to the time the regression spends in production: a time you reduce by detecting it before deployment.
How Long to Add Delta-QA to an Existing Cypress Setup
If you already use Cypress and want to add Delta-QA, here is what it concretely involves.
Delta-QA works independently of Cypress. You don't need to modify your existing Cypress tests. You don't need to install a plugin. You don't need to touch your Cypress configuration. The two tools coexist without conflict because they share nothing.
Setting up Delta-QA consists of opening your site and going through the scenarios to cover. The first run establishes the references. That's all: visual coverage is active, independently of your Cypress tests.
To go further in CI, Delta-QA now has an SDK, Vision. Today it covers Playwright, in TypeScript and JavaScript; Cypress support is planned next. With Playwright, one line per page to check is enough: an unreviewed difference makes the test fail, and the CI log gives the link to the report.
FAQ
Will Cypress ever add native visual testing?
It's a recurring question in the Cypress community. As of 10/2026, the documentation states that Cypress doesn't compare images itself and points to plugins. Cypress Cloud keeps growing (Test Replay, UI Coverage, Accessibility, AI features such as cy.prompt()), but without visual comparison to a reference. And even if Cypress added it, it would remain coupled to the execution of functional tests: which would keep the coupled coverage problem described above.
Aren't Cypress's visual plugins enough? For basic use, they can get you by. But they add a dependency on a third-party service (with its own license cost), they couple visual coverage to functional coverage, and maintaining them is an extra burden. If you have 10 pages and a developer available to maintain the plugin, it can work. If you have 100 pages and a mixed QA team, the limitations become blocking.
Can Delta-QA detect bugs that Cypress doesn't? Yes, by definition. Cypress checks programmatic assertions: "this element contains this text", "this URL is correct", "this request returned a 200". Delta-QA checks visual appearance: "this page looks identical to the reference version". Visual bugs (CSS regressions, responsive issues, z-index conflicts, missing fonts) are invisible to Cypress assertions but detected by Delta-QA.
Does Delta-QA slow down the CI/CD pipeline? Your Delta-QA scenarios recorded without code don't go through your Cypress pipeline: they don't slow it down. For CI integration, the Vision SDK covers Playwright today; Cypress is planned next.
Do I have to choose between Cypress Cloud and Delta-QA? No. They serve different goals. Cypress Cloud optimizes your Cypress functional tests: parallelization, failure replay, flaky test detection, interface coverage, and accessibility. Delta-QA covers visual comparison to a reference, which Cypress Cloud doesn't address. The two are complementary investments.
My QA team isn't technical. Can they use Delta-QA without developer help? That's precisely the use case Delta-QA was designed for. The no-code interface lets a QA tester, a designer, or a product owner configure, run, and interpret visual tests without any development skills. It's one of the fundamental differentiators compared to a Cypress plugin, which requires modifying JavaScript code to add visual capture points.
Can Delta-QA be used with a framework other than Cypress? Yes. Delta-QA scenarios are independent of any test framework: whether you use Cypress, Playwright, Selenium, TestCafe, or no framework at all, they work the same way. And for Playwright teams, the Vision SDK lets you add a Delta-QA check inside an existing test.
Conclusion: Don't Let Cypress Carry a Burden That Isn't Its Own
Cypress is a remarkable tool for what it does. But asking it to cover visual testing (via plugins, hacks, or jury-rigged CSS assertions) is imposing a mission it wasn't designed for. It's like fitting a sprinter with a 20-kilo backpack and being surprised that they're slower.
Free Cypress. Let it do what it does best: testing that your application works. And entrust visual testing to a tool designed for it.
Ready to cover the visual blind spot in your test suite? Launch your first comparison with Delta-QA, with a free account and no credit card. Try Delta-QA for free →