Transforming testing methodologies: From manual to robust strategies
summary
Team moves from manual UI checks to a hybrid Selenium framework plus Jenkins pipelines, BrowserStack (plus Percy for visual diffs), TestRail and Grafana dashboards. Releases shrink from ~6.5 features to 2 per deploy and scale from 162/year to ~1,149/year, enabling multiple daily deploys. A designated release boss gates merges and inspects visual regression. Measured failures drop from ~21% (2015) to ~2% now. Automation includes headless grid, mobile device targeting from analytics, and archived screenshots for compliance.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker background
- 3:04Identifying the testing issue
- 7:23Setting transformation goals
- 9:52Testing and release process evolution
- 16:11Changes in merges and testing
- 18:19Increasing test coverage
- 26:26Device usage analytics and strategy
- 28:33Making rapid deployment decisions
- 30:38Visual regression and comparison tools
- 35:30Deployments and performance goals
- 37:42Results and failure rate reduction
- 38:45Key takeaways and conclusion
- 39:27Q&A session
related talks
40mScaling testing & test automation without losing control
38mScaling Automated Testing & Architecture from Startup to Enterprise
38mFreeing up Selenium
32mClimbing the Mountain of CI/CD: A Tester’s Tale
46mA Practical Guide to Testing in DevOps
23mAdaptive Testing
41mShift Left, Shift Right and Improve the Centre
37mSelenium In the Enterprise: What went right, what went wrong (so far)