Automated on demand delivery of Browsers for testing with Selenium
summary
Delivers browser binaries from an internal maven repository on demand, with a plugin/task that resolves coordinates, downloads and extracts specific Firefox, Chrome and PhantomJS builds, and supplies the binary and driver to Selenium via capabilities. Handles Windows Chrome installer quirks, caches artifacts locally, and offers staging/preview/release channels so CI can lock versions or opt into updates. Integrates with Maven/Ant and IDE runs, added PhantomJS in under a day, and runs in production at MathWorks for over a year with reproducible cross‑browser CI.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 7:27The goals
- 11:59Possibilities!
- 17:30Questions that needed to be addressed
- 19:38Browsers in internal repository
- 21:35Adding a new browser version
- 22:29How do builds ask for browsers?
- 25:13Installing Browsers during a test cycle
- 30:09Edge cases
- 31:43The staging approach
- 34:39The need for a qualification process
related talks
47mTest Automation with Selenium 5 and Java
32mOld Tools, New Tricks: Unleashing the Power of Time-Tested Testing Tools
01h 13mThe multi-year quest for the best web test in the west
31mSelenium Hacks
30mLessons from testing browsers using WebDriver
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
46mWebDriverManager: the Swiss Army Knife for Selenium WebDriver
42mReliable and Maintainable Webdriver Tests