How do you implement visual regression testing and when is it worth it?
- visual regression
- screenshot testing
- UI testing
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Tools: Playwright visual comparisons, Percy, Chromatic, BackstopJS. When worth it: design-heavy applications, component libraries, marketing pages. Implementation: capture baseline screenshots, compare on each PR, review diffs in a dashboard. Challenges: handle dynamic content (dates, avatars) with masking, manage cross-browser/OS rendering differences, set appropriate diff thresholds. Not worth it for highly dynamic content like dashboards with live data.
What interviewers listen for
- Test architecture instinctsYou can defend why your suite is shaped like a pyramid, a trophy, or a honeycomb.
- Locator disciplineYou rank selector strategies by stability and explain when to break the rule.
- Flaky test ownershipYou debug to a structural fix instead of retry-until-green.
- Parallelisation literacyYou know how your framework isolates state, fixtures, and database access across workers.