TestOps: A Journey to Story-Based Releases
summary
Project moves from a broken main branch to story-based releases within one year by replacing ~50 separate repos with a single monorepo, using GitLab pipelines plus Helm charts on Kubernetes to build only changed components and spin up short‑lived dev environments. Teams get up to ~30 dynamic feature namespaces (lived hours to a sprint) and run isolation tests; end‑to‑end confidence comes from test catchers that validate outbound messages. Three people drive the ops work while teams adopt shift‑left testing.
AI-written summary · about
chapters (15)
- 0:00Introduction to TestOps and story-based releases
- 3:09Out of the frying pan into the fire
- 7:44The Council of Elrond aligning testing strategy
- 14:03The gathering storm microservices chaos
- 17:58The spark dynamic environments with Helm
- 22:30The Battle of Hogwarts end-to-end testing hurdles
- 28:53Lessons learned on the journey to releases
- 31:02Q&A addressing environment costs and support
- 33:28Q&A on ACC environments and feature flags
- 35:17Q&A handling critical hotfixes in production
- 37:00Q&A Helm vs GitLab tags and deployment strategies
- 39:08Q&A cloud costs and resource management
- 40:21Q&A quality gates and decision-making in pipelines
- 43:10Q&A migrating from multi-repo to monorepo
- 45:17Q&A team resources for test environments
related talks
28mTestOps: A Journey to Story-Based Releases
30mTestOps: Transforming Chaos into Streamlined Story-Based Releases
54mFrom Code to Customer
15mTransforming Testing: The Power of TestOps
32mClimbing the Mountain of CI/CD: A Tester’s Tale
34mGitOps for the people
25mDevOps Handbook Experiments in Accelerating Delivery
21mValue of DevOps Release Process in Data Teams