“The Yahoo! Story” How Yahoo! Embraced Automated Testing to...
summary
Yahoo Mail replaces biweekly, manual whiteboard testing and a fragile Java Selenium/TestNG VM grid with a pull request build that enforces unit and functional tests, a 75% code coverage gate, and fast feedback so commits merge within minutes. The team rebuilds tests in Ruby + Cucumber + WebDriver + Page Object, moves browsers to an external cloud grid (Sauce Labs), keeps master always deployable, eliminates rollbacks, and shifts ownership so developers write and maintain tests.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:26About Neil
- 1:21Agenda
- 2:19Yahoo Mail
- 5:12Release Cycle
- 7:13The Not So Good Old Days
- 9:36Negative Outcomes
- 10:26Solutions
- 11:20Outcomes of Solution 1
- 14:15Company Organization Changes
- 16:20Adopting Agile
- 20:24Cucumber
- 22:13Continuous Delivery
- 23:44Test in Isolation
- 25:01Pull Request Build
- 26:58Outcomes
- 28:50Challenges
related talks
25mManaging Changes Seamlessly on Yahoo's Hadoop Infrastructure Servers
53mTransforming testing methodologies: From manual to robust strategies
23mAdaptive Testing
45mHow to Make Developers LOVE Writing e2e Tests
39mWeb Apps don't need no manual testing
50mAsaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
05mTaming the Testing Beast
36mTest Automation to the Max