QA in a Pipeline Based Organization
summary
Claim: pipeline-driven orgs remove humans from tactical approvals by encoding decisions as tests that exit non zero to veto builds and let a pipeline be green drive promotion. Examples: Jenkins/TFS/TeamCity jobs, Docker and Kubernetes environments that spin up, test, and destroy. Practice built: a paired test recipe meeting (developer + test architect) embedded under the user story, with a 1:10 high-to-low test-level ratio, and pipelines that either pass or fail — reducing sign-off stress and enabling faster continuous delivery.
AI-written summary · about
chapters (19)
- 0:00Who works in QA
- 2:53Agenda
- 4:57Continuous Delivery
- 6:58Continuous Integration
- 9:55Pipelines
- 18:32Pipeline
- 22:59Developers
- 23:58Ops
- 25:28Security
- 26:38Tester
- 27:57Benefits
- 31:02How do we get there
- 33:33Test recipes
- 36:50Test plans
- 37:27Knowledge sharing
- 37:43The pyramid of maintainability
- 39:43A better representation
- 41:17The conversation
- 42:58Summary
related talks
52mCreating a QA/DEV Collaborative Testing Strategy
44mThe Pipeline Driven Organization｜
41mThe Pipeline-Driven Organization
30mQA in DevOps: Transformation thru Automation via Jenkins
29mWhy your next QA job might be in Ops
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
42mI Don’t Need No Tests
06mDoes QA have a place in DevOps? Heck yeah!