Blog

A design system lives or dies by the consistency of its application. Defining tokens, components and a brand chart is not enough — you still need to verify that every screen, in every product, actually respects those rules across releases. That is precisely the role of visual testing applied to a design system: detecting that a padding has drifted, that a button variant has been duplicated locally rather than reused, that a brand color has been replaced by a hardcoded value during a quick integration.

This page gathers articles dedicated to the design system / visual testing intersection: structuring a test suite by component and by page, managing baselines during token evolutions (palette changes, typography overhaul), articulation between component-level verification (Storybook + Chromatic typically) and assembled-page validation. We also address the organizational stakes: who validates the visual diffs — the design team, the front-end team, QA? How do you prevent visual debt from quietly piling up between two audits? Delta-QA focuses on the page layer, complementary to component tooling, and these articles aim to provide a holistic view rather than promote a single toolchain.