Revolutionizing Continuous Integration with Selenium
summary
Cars.com builds a Java + Maven Selenium framework integrated with BuildForge and Selenium Grid to run ~3,000 Selenium tests on ~600 JVMs per build, captures single-user performance with Dynatrace timers, and runs hourly builds for many products. Test cycle time drops from 235 hours to 4.5 hours — a 98.2% reduction — and some suites report 99% savings; the CI pipeline notifies failures, stores screenshots, and pinpoints regressions so devs can fix quickly.
AI-written summary · about
chapters (6)
related talks
35mMassively Continuous Integration: From 3 days to 30 minutes
38mFreeing up Selenium
05mTaming the Testing Beast
01h 00mAutomation Engineer’s Way to Continuous Integration
34mUsing Selenium to Improve a Team's Development Cycle
53mTransforming testing methodologies: From manual to robust strategies
48mCI With Bazel (Why Selenium is Using It & You Should Too)
43mInfinite Space for Your Tests