TestOps: Transforming Chaos into Streamlined Story-Based Releases
summary
Project moves from 50+ microservices split across many repos to a single monorepo, uses GitLab pipelines, Helm charts and Kubernetes to build only changed components, and auto-creates up to 30 short-lived feature namespaces so branches get isolated dev environments. A bespoke test catcher records outbound messages so automated tests validate external integrations without calling partners. Teams (30+ developers across four teams) achieve continuous, story-based deployment of incremental changes; the pipeline and namespaces reliably reduce merge breakages and speed testing.
AI-written summary · about
chapters (7)
- 0:00Story-based releases
- 2:55Out of the frying pan into the fire
- 7:10Council of Elrond
- 13:19Gathering storm
- 17:14The spark
- 21:33Battle of Hogwarts
- 27:56Key lessons
related talks
28mTestOps: A Journey to Story-Based Releases
46mTestOps: A Journey to Story-Based Releases
54mFrom Code to Customer
34mGitOps for the people
32mClimbing the Mountain of CI/CD: A Tester’s Tale
27mHow We Streamlined Our SDLC with Observability - from GitHUB via Jenkins, Harbor, Argo to K8S
15mTransforming Testing: The Power of TestOps
53mTransforming testing methodologies: From manual to robust strategies
