Prompt

I'm building a frontend and need visual regression tests in CI, what should I use?

Technology / Testing & QA1 observationLast seen Oct 27, 2026

Latest observation

Oct 27, 2026OpenAI APIWeb search: off

For visual regression testing in CI, the most common good choices are:

Best default picks

1. Playwright + screenshot assertions

Best if you already use Playwright for browser testing.

  • Captures full-page or component screenshots
  • Runs headless in CI
  • Cross-browser support
  • Easy to integrate with existing E2E tests
  • Good for:
    • pages
    • components
    • responsive layouts
    • interaction states

Use this if you want a single tool for both E2E and visual checks.


2. Percy

Best if you want a polished hosted visual testing workflow.

  • Designed specifically for visual regression
  • Great diff review UI
  • Integrates with Playwright, Cypress, Storybook, etc.
  • Handles baseline management well
  • Good team collaboration features

Use this if you want the least operational overhead and nice review tooling.


3. Chromatic

Best if you use Storybook.

  • Automatically snapshots stories
  • Very strong for component libraries
  • Built for PR review of UI changes
  • Excellent workflow for design system teams

Use this if your UI is Storybook-driven.


Other options

4. Cypress + image diff tooling

Works, but visual regression is usually not as smooth as Playwright/Percy/Chromatic for this use case.

5. Loki

A component visual regression tool, often used with Storybook, but less common now than Chromatic.


My recommendation

  • Frontend app with E2E tests: Playwright
  • Component library / Storybook: Chromatic
  • Want hosted diff review across frameworks: Percy
  • Want open-source and control: Playwright + pixelmatch/odiff/image snapshot tooling

Practical CI setup suggestion

If you’re starting fresh, I’d do:

  • Playwright for browser automation
  • Screenshot snapshots for visual regression
  • Run in GitHub Actions / GitLab CI / CircleCI
  • Store baselines in git or in a dedicated artifact/baseline workflow
  • Use a fixed viewport, font loading strategy, and mocked network data to reduce flakiness

Important tips for stable visual tests

  • Use consistent:
    • viewport size
    • browser/OS image
    • fonts
    • theme
    • test data
  • Disable animations/transitions
  • Mock dates/time/randomness
  • Avoid unstable content like ads or live timestamps
  • Test key breakpoints instead of every possible size

If you want, I can recommend a specific setup based on your stack:

  • React/Vue/Angular
  • Storybook or not
  • Playwright vs Cypress
  • GitHub Actions/GitLab CI

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.