What problem does it solve?
Visual regression testing prevents unintended UI changes by comparing screenshots pixel-by-pixel, so teams can detect layout, styling, and component regressions early in the development workflow.
Core Features & Use Cases
- Percy setup for screenshot diffs: Configure Percy with Playwright and optionally adjust snapshot viewports and Percy CSS to ignore dynamic UI noise.
- Chromatic for Storybook components: Enable visual checks for component libraries by running Chromatic with the proper project token and CI-friendly GitHub Actions configuration.
- Playwright native screenshot comparisons: Add self-hosted visual assertions using Playwright’s screenshot matching with tolerances to reduce false positives.
- BackstopJS self-hosted testing: Use BackstopJS to capture baseline screenshots and compare against new renders across multiple viewport scenarios.
- Best practices for stability: Hide or neutralize dynamic content (timestamps, random IDs) and disable animations to produce consistent, reviewable diffs.
Quick Start
Set up Percy with Playwright by installing the Percy CLI and Playwright adapter, adding a Percy snapshot test, and running the visual test script with PERCY_TOKEN configured in CI.