# Improving Frontend Regression Testing with Chromatic

DevFeed: [Improving Frontend Regression Testing with Chromatic](<https://devfeed.tech/articles/improving-frontend-regression-testing-with-chromatic-30794.md>)

Original publisher: [Read original article](<https://devblog.kogan.com/blog/improving-frontend-regression-testing-with-chromatic>)

Author: Stephen De Vaux

Published: 2026-01-30T01:00:49Z

Content type: article

Language: en

Sources: [Kogan.com](<https://devfeed.tech/sources/kogan-com.md>)

Topics: [Front end](<https://devfeed.tech/topics/frontend.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [Storybook](<https://devfeed.tech/topics/storybook.md>), [Remix](<https://devfeed.tech/topics/remix.md>), [browser](<https://devfeed.tech/topics/browser.md>), [ci](<https://devfeed.tech/topics/ci.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [pull-requests](<https://devfeed.tech/topics/pull-requests.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [unit test](<https://devfeed.tech/topics/unit-test.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [browser](<https://devfeed.tech/tags/browser.md>), [ci](<https://devfeed.tech/tags/ci.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [regression](<https://devfeed.tech/tags/regression.md>), [remix](<https://devfeed.tech/tags/remix.md>), [storybook](<https://devfeed.tech/tags/storybook.md>), [testing](<https://devfeed.tech/tags/testing.md>), [ui](<https://devfeed.tech/tags/ui.md>), [unit-test](<https://devfeed.tech/tags/unit-test.md>), [visual-regression-testing](<https://devfeed.tech/tags/visual-regression-testing.md>)

## AI overview

The article explains how Kogan integrated Chromatic into a Remix-based frontend testing workflow to detect visual regressions that traditional unit tests may miss. It describes Chromatic's Storybook integration, browser screenshots, baseline comparisons, CI workflow, and the differences between UI Review and Visual Tests.

## Source excerpt

After recently migrating our frontend to Remix, we took the opportunity to reassess how we approach frontend testing, particularly regression testing. While we already had unit test coverage, we identified a gap when it came to validating UI changes. This is where Chromatic became a part of our frontend testing strategy. This post outlines why we introduced Chromatic and how it fits into a Remix-based workflow. Even when application functionality remains unchanged, subtle visual regressions can still be introduced. Changes to spacing, typography, layout, or component states can easily slip through without being caught by traditional tests. What we needed was a way to automatically detect meaningful UI changes while still fitting into our existing development workflow. At the same time, it was important to avoid introducing a fragile or high-maintenance testing setup, one that adds overhead without delivering proportional benefit. Our implementation with Chromatic attempts to balance automation, reliability, and developer experience as a practical addition rather than an extra burden. Why Chromatic? Chromatic provides visual regression testing on top of Storybook. Instead of testing components purely through assertions, Chromatic renders components in a real browser environment and captures screenshots. These are then compared against a known baseline to highlight visual changes. The key reasons we chose Chromatic were: Automated visual diffs that are easy to review Integration with Storybook, which we already use for component development CI-friendly workflow that fits well into pull requests Chromatic offers two closely related features for reviewing UI changes: UI Review and Visual Tests. While they have some overlap of functionality, they serve different purposes and are designed for different levels of enforcement. UI Review is enabled by default, whereas Visual Tests are an optional feature. UI Review generates snapshots that highlight differences against a bas