Quality Engineering for DevOps Teams
summary
Claim: quality engineering makes the team jointly responsible for “suitable quality at the right moment.” Specifics: three risk classes (A/B/C), pick 5–10 indicators, use an Excel template from tmap.net to map items to quality attributes and intensity, and apply preventive detective corrective measures. Tooling examples: junit plus a code‑coverage add‑on that drove 75% code coverage stops blue screens, SonarQube and CICD pipelines. Practices: feature toggles, four‑amigos reviews, exploratory plus coverage‑based test design.
AI-written summary · about
chapters (16)
- 0:00Welcome
- 1:49About speaker and book
- 3:53Quality at speed
- 5:00Business value goals
- 7:29Measuring process indicators
- 11:48Delivery models overview
- 13:11Quality engineering defined
- 17:07Quality measures types
- 19:12Risk-based quality policy
- 21:19Shift left strategy
- 23:09Quality measure groups
- 26:43Applying measures to items
- 29:12Measure intensity template
- 34:13Testing techniques
- 37:10Experience vs coverage testing
- 40:41Q&A
related talks
01h 02mKEYNOTE: Quality Engineering Strategy to Grow From Testing to Built-in Quality
20mEnsuring Quality in DevOps Culture
46mPanel Discussion: Quality Engineering - an Evolution of Software Quality as a Team Responsibility
12mConvergent Quality Engineering
01h 02mQuality for DevOps Teams
14mThinking of Quality as developer productivity tool
22mQualityOps–Left Shift Customer Success With A Thriving Quality Engineering Ecosystem
56mControlling Quality in Software Development