Why Testing is fundamentally different in DevOps than Classic Projects
summary
Workshop runs exercises from Liberating Structures, collects posters listing concrete fixes like one‑click speak up, reserve time to measure, pair programming and trunk‑based development. Claims: testing in DevOps is an ongoing activity not a separate phase, machines do checking while people do exploratory testing, whole team owns quality. Data: quick warmup shows ~5–20% see testing behind, an experiment introduced 10 artificial bugs and testers miss some which leads to asking for more resources. Practical takeaways include test data strategies, flaky test reduction, and clear Definition of Done.
AI-written summary · about
chapters (4)
- 0:00Start
- 19:45Helping to build the BEST system
- 20:57Whole team takes responsibility for quality
- 26:52is your take away?
related talks
47mHow Testing is Evolving in DevOps
15mTransforming Testing: The Power of TestOps
38mHow Testing is Evolving in DevOps
37mThe Role of Testing in Devops
44mWe’ve Got DevOps — Let’s Fire All Testers
27mExploring a DevOps Transformation Like a Tester
26mThe Impact of Testing on a DevOps Pipeline
25mDevOps Bringing a New Concept to Software Quality