Transformative Culture
summary
Revives a neglected UI automation suite, replaces noisy failures with a gated pipeline, and grows trusted checks from 33 to 165 tests while cutting full-suite runtime from about an hour to roughly 30 minutes. Migrates infrastructure to Mesos and Docker with Jenkins pipelines for per-branch builds, enforces a documented definition of done, uses risk analysis and a quarantine strategy to prioritize and stabilize tests, embeds CI and feature engineers on a dedicated Engineering Productivity team, and shifts ownership to scrum teams rather than writing tests for them.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 1:36A major challenge at Blackboard
- 4:16We needed a leader
- 5:45No longer referred to ourselves as QA
- 6:25Mission Statement
- 9:19Team Structure
- 14:23Documentation
- 16:14Test suite definitions
- 17:06Goals for each suite
- 18:01Gate
- 18:20Requirements
- 19:02Tooling
- 19:40Ownership
- 20:11Environments
- 20:39Containerization
- 21:03Migration to Mesos
- 21:34Jenkins Pipeline
- 22:40Consulting Phase
- 25:43Framework Support
- 27:07Quality Risks
- 29:59Risk Priority
- 30:49EndtoEnd Tests
- 31:31Lessons Learned
- 32:41What is critical
- 33:00Risk analysis
- 33:17Scale back
- 34:47Organizational questions
- 35:10QA organization
- 39:14QA sprint
- 39:30New department name
- 41:20Put a gate on in tests
related talks
40mScaling testing & test automation without losing control
38mScaling Automated Testing & Architecture from Startup to Enterprise
52mHow to win with automation and influence people
36mShifting Left: How to Build a Culture of Testing
39mTrust Issues With UI Automation
36mContinuous Integration For The Win!
39mBuilding The Blocks of Trust In Automation
32mTales from the DevOps Transformation Trenches