Freeing up Selenium
summary
Claims that Selenium/WebDriver should stop duplicating manual regression and instead power monitoring, CI and delivery pipelines. Demonstrates concrete tactics: post to API setup and no UI setup or teardown so tests only perform minimal UI actions; move tests into the team language and repo (migrated off Java and Sauce Labs to in‑repo Scala + CircleCI); runs production loop checks every minute and reports ~99.95% reliability; shows these services speed tests and make CI-driven releases practical.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 3:55Outline
- 8:02WebDriver
- 13:45Rules
- 14:40Keep it simple
- 16:28Make good technical decisions
- 18:11Make things testable
- 20:19Keep you I steps to a minimum
- 21:37Dont do any setup
- 22:28Dont preserve
- 22:54Simple rules
- 24:19Backstory
- 25:07Steps
- 26:19Testing Rules
- 27:15Testing Environment
- 28:53Testing Infrastructure
- 30:21UI Testing Tools
- 31:52Testing the UI
- 33:06Cleaning up a test
- 35:01Recruitment
- 35:47Reliability
- 36:41Testing
related talks
37mSelenium In the Enterprise: What went right, what went wrong (so far)
53mTransforming testing methodologies: From manual to robust strategies
34mUsing Selenium to Improve a Team's Development Cycle
01h 14mContinuous Testing
30mRevolutionizing Continuous Integration with Selenium
50mTesting in Production – dangerous, scary or better?
23mAdaptive Testing
46mA Practical Guide to Testing in DevOps