Interview with Neil Manvar
summary
Selenium automates real browser actions for functional tests across desktop and mobile and runs suites in parallel on a grid; Selenium starts in 2004 and merges with WebDriver around 2007–2008 into Selenium WebDriver (Selenium 2). Modern single‑page apps require wait for conditions instead of relying on full page loads, and flaky async JS means tests must be integrated into CI with gating rules like CI-enforced tests and parallel cross‑browser runs and addressed promptly.
AI-written summary · about
related talks
34mUsing Selenium to Improve a Team's Development Cycle
27mKnowing your automation
33mBringing Selenium to the Rest of the Company
28mFrom Resistance to Results: Navigating a Test Automation Tool Shift
30mEnd to End Testing: The Game Has Changed
40mSelenium and the Four Rules of Simple Design
29mAutomated Testing 101/Testing Web Apps 101
07mInterview