Scaling up with Embedded Testing
Talkat CAST 2014 · on Tuesday, 2014-08-12· at 12:45· 10th fl Rosenthal Pavillion, Kimmel Center for University Life·
summary
Teams remove separate QA and embed testing into development with measurable wins: Google reports over a thousand releases and shifts to 80–90% weekly releases, fewer rollbacks and shorter cut-to-push times. Engineering groups hire or rotate specialists (SETs) to build catalytic infrastructure — CI, integration suites and reusable test frameworks — and pair them with developers so tests and fixes happen in the same loop. Cloud Foundry drops a QA department but keeps test experts who coach teams; Microsoft shifts to generic employee teams with overlapping skills.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:43Manual Testing and Automated Testing
- 11:44Elizabeth Hendrickson
- 18:27Michael Bachman at Google
- 25:53Hiring
- 26:55Release Management
- 32:13Project Management
- 43:42Pairing with Developers
- 43:58Providing Visibility to Teams about Testing Problems
- 44:58How Do You Get the Developers To Be Even Interested in Learning How To Test They Already Have Developer Jobs
- 45:22Pivotal Dna
- 47:51Kimberly Ellsworth
- 1:03:29Quality Group Ownership of Quality
related talks
59mAgainst a Harmful Divide: Testing as the Lifeblood of Development
49mThe Whole Team Approach to Testing in Continuous Delivery
36mHow programmers & testers can be productive
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
13mFewer Tools, More Impact: An Automated Testing Strategy for Scale-Up
36mWhy a Growing Company Needs a Growing QA Team
41mShift Left, Shift Right and Improve the Centre
45mIs there a place for QA in modern agile autonomous fast-flow teams?