Selenium Committers Panel Discussion

on YouTube ↗44m

" summary

Panel Q&A summarizes concrete decisions and work: WebDriver will not expose HTTP status codes — use a proxy or Chrome/Opera devtools instead; Selenium 3 focuses on mobile, and Selenium RC moves to selenium-legacy as a separate download; Safari driver remains the missing piece for full browser coverage; practical problems addressed include brittle stale-element errors, slow chatty HTTP wire protocol (proposal to explore a binary protocol), fragile screenshots, file uploads and native dialogs, and CI scale (about 4,000 hours/month reported).

AI-written summary · about

" chapters (11)

1. 0:00Introduction and panel
2. 1:45Meet the team
3. 4:24HTTP status codes
4. 7:57The future of Selenium
5. 12:21Tooling and browser drivers
6. 17:58PHP bindings and support
7. 20:21Cross-browser testing
8. 24:02Screenshot challenges
9. 26:18Security and browser vendor risks
10. 33:33Desired API features
11. 40:37Conference wrap-up

" related talks

• 55mQ&A with the Selenium CommitteeSelenium Conference India 2018
• 42mCommitters PanelSeleniumConf London 2019
• 55mSelenium Committers Panel TalkSelenium Conference 2011
• 50mSelenium: State of the UnionSimon Mavi Stewart · SeleniumConf India 2020
• 52mSelenium: State of the UnionSimon Mavi Stewart, Manoj Kumar · Selenium Conference India 2018
• 52mSelenium: State of the UnionSimon Mavi Stewart, Manoj Kumar · SeleniumConf India 2020
• 40mSelenium State of the UnionSimon Mavi Stewart · Selenium Conference 2013
• 49mSelenium: state of the unionSimon Mavi Stewart, Jim Evans · SeleniumConf Chicago 2018