render-reftest

Pixel diff tests prevent visual regressions by rendering fixtures via headless Chromium through Playwright, generating per-fixture PNGs, and comparing them against independent reference images to detect visual inconsistencies across backends.

A reftest validates against an independent oracle, a golden test compares against snapshot baselines, and a probe test executes pixel assertions without vision; this workflow guides selecting the appropriate strategy and constructing robust fixtures for each.

Yes, you can validate Figma refig pipeline outputs by integrating browser-based diff workflows; the pipeline requires a suite.json describing fixtures and uses Playwright's headless Chromium to render and validate the visual outputs.

To generate oracle PNGs and run visual diff reports, define your fixtures in a suite.json file, render the suite through the reftest pipeline using headless Chromium, and output per-fixture PNGs alongside a compatible diff report.

The best way to structure fixtures for browser-based visual regression testing is to define them in a suite.json file, enabling the testing pipeline to systematically render each fixture and validate outputs against independent references or golden snapshots.

Yes, a suite.json file is required to run visual rendering tests; it describes the fixtures used by the pipeline to render outputs via headless Chromium and generate the corresponding PNGs and diff reports.