Life After Selenium
summary
Selenium era WebDriver tests date from 2004 and rely on REST polling which makes UI checks flaky and slow, a 100 ms added latency breaks the same test. WebDriver and webdriver.io runs fail with NoSuchElement while switching to puppeteer via the Chrome DevTools Protocol succeeds because CDP event-driven control gives real‑time browser events. Cypress runs show live demo failures but allow network stubbing in Cypress to replace API payloads on the wire and pass. Selenium 4 promises bi‑directional CDP support.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:07What is Selenium
- 4:39Selenium Test
- 6:01Why is Selenium flaky
- 7:31Solutions
- 11:53WebDriver
- 13:29Puppet
- 19:48Live Demo
related talks
53mCypress vs Selenium Wrappers
41mDesign Decisions for Perfect JavaScript Testing Framework
31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and its Integration with Selenium
53mSelenium 4.0 and W3C: What You Need to Know
26mHow browser automation works behind the scenes
09mPros and cons of UI testing tools
20mSelenium 4 – What's New and How you Can Use it!
18mModern Solutions for e2e testing