Codeless Visual Testing
summary
Argues that record‑playback tools become practical visual testers by pairing Selenium Builder with Applitools to drive and compare full‑page screenshots, producing a codeless visual test for GitHub that runs, finds unexpected layout diffs, and lets reviewers accept or reject baselines. Claims next‑gen Selenium IDE revival and notes IDEs reach 100,000 users. Notes remaining limits: linear control flow and tool dependency, but simpler interactions and fewer brittle selectors make migration and export to Selenium code far easier.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:48Selenium IDE
- 4:52Follow the project
- 6:04Record playback tools
- 6:59My personal opinion
- 8:23Skills required
- 8:45Understanding how browsers work
- 10:32Understanding selectors
- 11:54Software engineering
- 12:32Control flow
- 13:15Program language
- 13:35Cons
- 13:55Conclusion
- 14:29Visual Testing
- 16:10How does it work
- 16:41What are images
- 18:10Summary
- 19:59Tool Dependency
- 20:25Demo
- 25:19Conclusions
related talks
39mCodeless Visual Testing
46mHow I learned to stop worrying and love record and playback
37mThe Colorful World of Visual Test Automation
42mHow Visual AI Makes Testing Easy
41mAdvanced test automation techniques for responsive apps and sites
43mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
37mSpot the Difference; Automating Visual Regression Testing
37mAdvanced Test Automation Techniques for Responsive Apps and Sites