Taming the Testing Beast
summary
A once-mighty Java-based framework drives browser sessions via Selenium grid to run 150 acceptance tests that take 5 hours of script time. Configurations move from code to spreadsheets, then to web-captured workflows that emit skeleton automation for developers. That pipeline initially stabilizes quality, but moving the framework ownership across two teams causes coordination friction, broken tests and escaped bugs, and the cure becomes heavier process and bureaucracy rather than sustainable shared ownership.
AI-written summary · about
related talks
01h 14mContinuous Testing
53mTransforming testing methodologies: From manual to robust strategies
30mRevolutionizing Continuous Integration with Selenium
38mFreeing up Selenium
35mBuild an automation framework... with a developer mindset
29mState of Web Integration Testing
52mHow to win with automation and influence people
37mFrom Rigidity to Resiliency: An Evolutionary Tale of Selenium-Based Frameworks