Holistic cross browser testing with Selenium
summary
Functional Selenium tests pass while visual layout fails: two-page example across six browsers creates 12 manual checks but automated analysis finds 14 differences and returns a grade F. System combines DOM metrics, computer vision and rule sets; snapshots are captured via Red Glass (Ruby gem) during RSpec/WebDriver runs and sent to Dom Reactor for scoring. Jenkins build-flow gates use the layout result so a failed layout breaks the build; Appium, Sauce and remote WebDriver are supported.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:41ABOUT
- 1:40MOTIVATING EXAMPLE
- 3:56GENESIS OF THE PAIN
- 4:38EXAMINING THE PAIN
- 5:27ISOLATING THE PAIN
- 6:18LAYOUT ANALYSIS
- 6:59INTEGRATED APPROACH
- 8:28DOM EXAMPLE
- 8:59DOM PROBLEM
- 9:52COMPUTER VISION
- 10:57CV EXAMPLE
- 11:39CV PROBLEM
- 12:08RULES
- 13:14RULE EXAMPLES
- 14:12RULE PROBLEM
- 15:10INTEGRATED EXAMPLE
- 17:39POWERFUL, BUT ISOLATED
- 18:16CONTEXT IS KING
- 18:45MUTATION EVENTS
- 20:12REDGLASS USAGE
- 20:45REDGLASS IN ACTION
- 22:48CAPTURING STATE
- 23:07TAKE_SNAPSHOT
- 24:04REDGLASS + DOMREACTOR
- 26:43POWERFUL, INTEGRATED
- 28:42CONTACT
related talks
37mSpot the Difference; Automating Visual Regression Testing
43mYour Tests Lack Vision: Adding Eyes to Your Automation Framework
30mImplementing a Visual CSS Testing Framework
18mImplementing a Visual CSS Testing Framework
40mWhy Does a Layout Designer Need Selenium
42mAutomated CSS Testing
27mAutomate Responsive Website Testing
41mAdvanced test automation techniques for responsive apps and sites