Chromatic

8 July 2025

🚀 Chromatic's Accessibility Testing & Dashboard are now live! Powered by Storybook & axe, we're making accessibility compliance seamless across your entire dev lifecycle—without slowing you down.

In two days, your React Native stories become visual tests with Chromatic. 📱 No test scripts, devices to maintain, or test flake. Every story is snapshotted on iOS and Android, and shows reviewers exactly hat changed. Join for a live demo from local build to review and Q&A 👇

🔗 Register here: us02web.zoom.us/webinar/regi...

Chromatic reposted

Storybook

@storybook.js.org

How are agents really doing on your frontend? 🤖 Are they saving you work or shipping a button that’s 2px off? Tell us in the State of AI in Frontend Delivery 2026 survey. It takes 5 minutes and 5 people get a $75 Amazon gift card as a thank you. 🙏 Survey in comments👇

📣 New in Chromatic: Quarantine for flaky tests You can now quarantine the flaky diffs that slip past Chromatic’s automatic filter. Quarantine the test from its build or test page to get your PR moving. 🧵⤵️ (1/5)

View full thread

In Library > Quarantined, you can see each test’s issue rate. Fix the flake, remove quarantine, and put the test back to work. While quarantined, it won’t catch regressions. (4/5)

chromatic.comQuarantine flaky testsUnblock your PR now. Track and fix flakes later.

Read the full announcement: chromatic.com/blog/quarantine-flaky-tests (5/5)

Chromatic keeps capturing snapshots for quarantined tests, but ignores their diffs across builds, branches, and users. So the same flaky diff won’t keep showing up for review. (2/5)

The test doesn’t disappear. Quarantined diffs show up in the build’s Unstable group, alongside tests caught by the automatic flake filter. Expand the group to inspect them. (3/5)

Our new @vitest.dev plugin turns the tests you already have into visual tests. 📖 No Storybook required ✍️ No changes to your test code Join @ariperkkio.dev, the Vitest core maintainer who built it, and @kylegach.com live tomorrow. 🧪 🎟️ Save your spot 👇

us02web.zoom.us/webinar/regi...

@vitest.dev already renders your components in a real browser. Now you can visually test them there, with no test code changes. 🎙️ @ariperkkio.dev, the Vitest core maintainer who built our new plugin, is doing a live walkthru with @kylegach.com to show you how. 🎟️ Save your spot 👇

👉 Register here: us02web.zoom.us/webinar/regi...

3 Sept

Chromatic for @vitest.dev Browser Mode is live. 🧪📸 Browser Mode runs your component tests in a real browser. Now Chromatic checks how those components look by capturing the rendered UI. No new screenshot assertions. No second suite to maintain. 🧵 (1/4)

Run your tests as usual. Chromatic then: ✔️ Compares snapshots across stable cloud browsers ✔️ Runs every browser and viewport in parallel ✔️ Surfaces visual changes in your PR for team review ✔️ Stores the full rendered UI behind every diff (3/4)

chromatic.comIntroducing Chromatic for Vitest Browser ModeVisual testing for Vitest Browser Mode, built for teams

3 Sept

📖 Read the full release: www.chromatic.com/blog/introdu... (4/4)

Vitest core maintainer, @ariperkkio.dev, built the plugin around Browser Mode tests. As your tests run, Chromatic captures a web archive of each result: the HTML, CSS, JS & assets behind the UI. When something is off, open that exact state in a browser instead of debugging a flat screenshot. (2/4)

2 Sept

iOS is now available for React Native visual testing on Chromatic 📱 Chromatic now builds your Storybook app for iOS and runs your visual tests on the iOS simulator. 👉 Request beta access to get started: share.hsforms.com/1Bjqi15TSS3m...

This month we’re rolling out two changes to help you test more with fewer snapshots. 🔀 Builds that don’t touch UI are free 📊 New Trends dashboard to help you investigate usage spikes 👇

Trends dashboard charts all factors that affect billed snapshots: no. of builds you run, snapshots generated by each build, and the average cost per snapshot. This helps you see what's driving usage usage and investigate unexpected increases.

chromatic.comChromatic changelog: August 2026Bypassed builds are now free, and new Trends dashboard to help investigate usage increase

Read the full announcement: www.chromatic.com/blog/chroma...

This month we’re rolling out two changes to help you test more with fewer snapshots. 🔀 Builds that don’t touch UI are free 📊 New Trends dashboard to help you investigate usage spikes 👇

TurboSnap now bypasses builds when there are no changes in any story’s dependency graph within that build. Nothing is captured, nothing is copied, and you’re charged zero snapshots.

6 Aug

Our upcoming public API lets agents test their own frontend work, diagnose what failed, and fix it in the same loop. Join Jarel Fryer and Varun Vachhar for a live preview and our roadmap for agents. Register in comments 👇

6 Aug

🎟️ Register to join: us02web.zoom.us/webinar/regi...

Flaky tests shouldn't block your build. Meet Flake filter: Chromatic now auto-detects unstable tests, so you can focus on real changes without getting blocked by flakes. 🧵

Bonus: you can now ignore any test manually too. New story not ready for review? Weird diff after a rebase? Set it aside and come back later.

chromatic.comAutomatic flaky-test filteringChromatic now auto-detects unstable tests, so you can focus on real changes without getting blocked by flakes

Flake Filter is live on every plan, on by default, with no setup required. Read the full announcement » www.chromatic.com/blog/automat...

Flaky tests shouldn't block your build. Meet Flake filter: Chromatic now auto-detects unstable tests, so you can focus on real changes without getting blocked by flakes. 🧵

Chromatic re-evaluates every test on every build. When a test stops flaking, it automatically rejoins the test suite.

Ignoring a flaky test doesn't mean ignoring the problem. Every unstable test gets a Playwright trace attached automatically (network, console, DOM) ready to reivew when you are.

Flaky tests shouldn't block your build. Meet Flake filter: Chromatic now auto-detects unstable tests, so you can focus on real changes without getting blocked by flakes. 🧵

Flake Filter renders every test multiple times to check its stability. Unstable ones move into an auto-ignored group. Their diffs stop blocking your build.

Chromatic reposted

Storybook

@storybook.js.org

9 July

The frontend bottleneck is no longer code generation. It's now reviewing the output of an agent. Storybook is working on two things to fix that: ✅ Claude Code + Codex plugins ✅ Agentic review to surface key changes Join Storybook team for a live walkthrough + Q&A. Register in comments 👇

Chromatic reposted

codrops

@codrops.bsky.social

24 June

Visual bugs don't always show up in your test suite. Kyle Gach from Chromatic shares how visual testing complements Vitest Browser Mode, helping catch the layout, styling, and responsive regressions that traditional component tests can miss. Early access is now open: tympanus.net/codrops/?p=1...

11 June

Get first access to our @vitest.dev plugin, which adds Chromatic’s visual testing and review to your browser tests. It’s built by @ariperkkio.dev, a Vitest core maintainer. It’s free to use while in beta and requires no changes to your test files. Read on for more info 🧵

Vitest already has visual testing. How is this better? ✔️ Fast and reliable servers consistently snapshot components in parallel ✔️ Automatically detect and reduce flakiness ✔️ Review and debug the real code behind your components, not screenshots

chromatic.comVitest Visual Testing sneak peekFast, reliable visual tests, debuggable snapshots, collaborative review

11 June

Why should I sign up for the early access program? ✔️ You (want to) test UI components with Browser Mode ✔️ You want hands-on support and free snapshots while in beta ✔️ You want to shape the experience to fit real needs Learn more and sign up here: www.chromatic.com/blog/vitest-...

Why visual test? For UI, checking that something works with functional tests doesn’t tell the full story. Your Add to Cart button may technically be clickable, but if it looks untrustworthy or broken, no one will click it. Visual tests guard against that, with no extra code.

9 June

AI gets you to prototype fast. The hard part is proving the next prompt didn’t break the UI. Join @bolt.new CEO, Eric Simons and Chromatic CEO, Zoltan Olah for a live session on taking AI-generated UIs to production with visual tests + human review. Register in comments👇

9 June

🎟️ Join live & get the recording: us02web.zoom.us/webinar/regi...

28 May

We’re launching early access for Vitest visual testing with Chromatic! ⚡️ Built with @vitest.dev core maintainer ariperkkio.dev, Chromatic adds visual testing to the browser tests you already write. 🧵 (1/4)

Chromatic captures the states your tests create so you get: 📸 Snapshot real interaction states 🧪 Run tests in a stable cloud environment 🛠️ Debug rendered UI, not flat screenshots 🔎 Review visual changes before merge (3/4)

chromatic.comVitest Visual Testing sneak peekFast, reliable visual tests, debuggable snapshots, collaborative review

28 May

If you’re using Vitest Browser Mode, we’d love your feedback. Request early access 👉 www.chromatic.com/blog/vitest-... (4/4)

Your assertions can pass while the UI is still broken. → broken layouts → missing styles → bad interaction states → visual regressions after user flows (2/4)

20 May

📱Announcing beta Chromatic support for visually testing React Native apps! If you already use Chromatic, this workflow should feel familiar: Push a change → Chromatic captures rendered native UI → visual regressions show directly in your PR. 🔍✨ (1/3)

20 May

- 📱 Native: Devices run on native macOS & Linux simulators - 🏎️ Fast: Parallel tests by default - 📷 No flake: Battle-tested stabilization algorithm - 📙 Unified testing: Powered by React Native for Storybook - 🔍 Full review: diff checker, baseline tracking & PR checks (2/3)

chromatic.comReact Native visual testing sneak peekTest on real iOS and Android simulators, fast and flake-free.

20 May

We’re rolling out early access to a small group of teams first, while we continue refining this workflow. Request early access to get started: chromatic.com/blog/react-n... (3/3)

Chromatic reposted

Storybook

@storybook.js.org

12 May

Is your component library lighting up in errors and not sure how to tackle it? 👀 On Thursday, we’re showing how teams use parallel AI agents with Storybook + Chromatic to triage, fix, validate, and retest accessibility issues simultaneously. Register in comments 👇

6 May

Many a11y issues are repetitive, straightforward, and ideal for parallelized AI workflows. 🤖 Learn how to use Storybook + Chromatic to: ✅ Detect issues ✅ Parallelize remediation ✅ Use AI agents to fix + retest ✅ Validate fixes in Storybook 🎟️ Register in comments 👇

6 May

Join us live and get the recording: us02web.zoom.us/webinar/regi...

17 Apr

Our April changelog is out: 🔀 PR comments: Your test results and Storybook link right in the PR comment 🫨 Auto Playwright traces on unstable snapshots (no rerun needed) 🤖 Publish your Storybook MCP so agents reuse your approved components Read the full changelog 👇