Q & A with the Selenium Committer's Panel
summary
Live Q&A covers how people actually get started and stay contributing: first commits were docs or tiny fixes, reproduce issues and run the test suite to help triage, and steady 30–60 minute efforts beat burnout. Technical updates include BiDi/WebDriver work on GitHub and a public WG — join the W3C meetings — plus a planned summit to align Selenium with testing frameworks. Also discussed: realistic boundaries (Selenium = browser automation, not an all‑in‑one test runner) and quirky non‑test uses.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:36Lambda Test Winners
- 13:06David Burns
- 37:48What's the Silliest Thing People Have Wanted To Use Selenium
- 39:11If We Have any Plans To Build Api Testing Automation Directly within the Selenium








