2 articles
Each front-end framework brings its own challenges to visual testing. React works well with component-oriented tools like Chromatic or Storybook; Angular imposes its change detection cycles and its specific SSR rendering; Next.js mixes server-side rendering and client-side hydration, which complicates capturing a stable state; Vue and Svelte each have their specifics regarding transitions and scoped CSS handling. Understanding these nuances avoids blaming the testing tool for a framework issue — or the other way around.
The articles on this page explore visual testing integration in the main frameworks: recommended configuration, handling of framework-specific animations and transitions, clean disabling of Suspense or skeletons during capture, choice between component-level testing (with Storybook tooling) and page-level testing (with a tool like Delta-QA). We also cover delicate migrations — moving to Angular 17 then 21, Next.js upgrades with the App Router, React refactors toward Server Components — which are all moments where solid visual coverage prevents silent regressions. The goal is to provide concrete recipes, framework by framework, rather than generic talking points.
With a headless CMS, content changes without touching the code. But every editorial modification can break your layout. Visual testing is the only reliable protection against these invisible regressions.
Read more →Angular has specificities that complicate visual testing: change detection, zones, Material Design. Discover how visual testing compensates for Angular's complexity and which tools to use in 2026.
Read more →