Q&A with the Selenium Committee

on YouTube ↗55m

" summary

Open Q&A covers concrete gaps and fixes: W3C protocol migration already in Selenium 3 and tooling moves drivers to browser vendors, with Safari tech preview updating frequently; HTTP/OS auth dialogs are not specified so people use REST-auth plus cookie as a workaround; flaky end-to-end failures usually come from infra or app timing—capture screenshots/videos and use explicit waits; Angular apps benefit from Protractor or framework hooks; contribution advice is small, reviewable PRs, run the tests locally and nudge on Slack/IRC; community governance, code of conduct and diversity targets (26% women now, aiming higher) are discussed.

AI-written summary · about

" chapters (14)

1. 0:00Selenium Committee intro
2. 3:52First audience questions
3. 10:01Shittiest moments in Selenium history
4. 16:44Open floor Q&A
5. 21:01Selenium in regulated environments
6. 22:53Handling auth pop-ups
7. 25:00Driver updates and Safari support
8. 27:08Contributing guidelines
9. 34:27Selenium used for nefarious purposes
10. 39:32Debugging flaky tests
11. 43:15Selenium with AngularJS
12. 45:05Selenium as browser automation
13. 46:29Diversity in Selenium
14. 50:11Closing remarks

" related talks

• 44mSelenium Committers Panel DiscussionSeleniumConf 2012 London
• 01h 02mQ & A with the Selenium Committer's PanelPooja Shah · Selenium Conf 2022
• 42mCommitters PanelSeleniumConf London 2019
• 52mSelenium: State of the UnionSimon Mavi Stewart, Manoj Kumar · SeleniumConf India 2020
• 47mKeynote - Selenium: State of the UnionSimon Mavi Stewart · SeleniumConf Austin 2017
• 46mSelenium WebDriver Q&A panelSelenium Camp 2017
• 44mClosing Keynote: Q&A With the Selenium CommittersSeleniumConf Austin 2017
• 28mOpening KeynoteJason Huggins · Selenium Conference 2011