Adding a second pair of eyes with visual testing
summary
Shows a concrete workflow: add the Applitools Eyes Cypress SDK via npm, run Cypress to create a visual baseline, then rerun against a faulty build where Eyes flags a visual diff. Visual testing catches a z‑index/overlay bug that functional Cypress assertions miss and prevents checkout. The demo uploads DOM snapshots to Applitools, compares screenshots across viewports with Applitools Eyes visual AI, offers root‑cause highlights, and reduces flaky selector‑based tests while preserving CI automation.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:31Bugs Happen
- 3:50Let's talk about testing!
- 4:05Why is testing important?
- 6:15Why is testing hard?
- 7:48Visual Testing
- 9:16Cypress
- 12:11How does it work?
- 13:38Demo
related talks
23mAdding a Second Pair of Eyes with Visual Testing
27mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
21mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
41mYour 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
43mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
56mYour Tests Lack Vision: Adding Eyes to Your Automation Framework