Selenium Committers Panel Talk
summary
Panelists argue that Grid stays because teams need easy parallelism and shared infrastructure while others replace Grid with Jenkins agents instead of Grid for CI simplicity; WebDriver becomes the common protocol unifying Selenium and Watir; HTMLUnit and headless WebKit scale tests fast but fail real-browser fidelity; load testing with thousands of browsers is rejected in favor of JMeter or server-side tools; header injection is delegated to BrowserMob proxy; synchronization relies on implicit waits and targeted element waits.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:18Selenium Grid future
- 5:54Selenium vs WebDriver APIs
- 8:31Selenium for load testing
- 11:02Headless browsers
- 14:42Test dependencies & parallel execution
- 17:59Selenium to GitHub move
- 21:34Firefox profiles & remote WebDriver
- 24:05Selenium 1 vs WebDriver extensions
- 28:08WebDriver lacks extensions
- 30:17HTTP headers injection
- 34:23Mobile automation tools
- 38:00Waiting for page loads
- 41:35Selenium vs WebDriver proxy
- 47:21Browser support differences
- 50:12OS window control
- 52:49Client-side certificates
- 54:13Avoiding golden hammer







