Your Tests Lack Vision: Adding Eyes to Your Automation Framework
summary
Shows that adding visual validation (Applitools) to Cypress tests finds real issues DOM assertions miss: misaligned buttons, text off-page, hidden labels, flipped book order. Workflow: take baseline screenshot, send to Applitools cloud, run regression screenshots, ML compares with options like layout match level or strict/exact, mark unresolved for human review. Demo flips book order and fails, scopes region tests to avoid noise, and runs cross‑browser/device renders; the integration works and catches UX regressions current assertions let slip.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:14Inattentional Blindness
- 3:11Intentional Blindness
- 4:05Visual Bugs
- 8:08What Is Visual Testing
- 10:09Pixel to Pixel
- 12:53Add Visual Testing
- 13:42Visual Testing
- 14:14Delete Code
- 15:25Applicant Tools Dashboard
- 20:03Drawbacks
- 21:04Testing on Dynamic Layouts
- 22:48Dynamic Testing
- 24:33Cross Browser Testing
related talks
21mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
41mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
43mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
38mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
44mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
56mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
33mAdding a second pair of eyes with visual testing
36mVisual Validation - The Missing Tip of the Automation Pyramid