Your Tests Lack Vision: Adding Eyes to Your Automation Framework
summary
Automated DOM assertions miss UX and visual regressions so visual validation uses screenshots plus ML comparison to catch misaligned labels, color changes, overlap, responsive and localization issues. Demo shows integration into existing Selenium tests via Applitools Eyes, explains match levels like layout match level, scoping to elements, ignore regions, root‑cause diffs, and a visual grid that renders one captured state across many browsers/devices. A single-line CSS flip that leaves DOM assertions green but fails visual checks makes the case.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:22Attentional Blindness
- 6:12Opentable
- 9:20Visual Validation
- 11:39Eyes Api
- 12:30Add Eyes to an Existing Test Framework
- 15:46Visual Testing
- 16:42Set the Api Key
- 22:52Check Element
- 35:35Set Match Level
- 37:58Root Cause Analysis
- 38:27Cross-Platform
- 38:41Cross-Platform Testing
related talks
56mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
41mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
21mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
44mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
27mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
38mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
54mVisual Validation
36mVisual Validation - The Missing Tip of the Automation Pyramid