k-branches: How Not to Abandon Feature-Branch Testing When Moving to Microservices
summary
Discusses challenges of functionally testing feature branches when moving from a monolith to microservices, noting that testing linked services is harder. Compares approaches such as a single staging environment with manual coordination, shifting testing left (earlier in the pipeline), and using canary deployments, and explains how to keep testing feature branches viable in a microservices architecture.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 10:05Feature testing in microservices
- 19:00Dynamic routing implementation
- 29:14Context loss prevention
- 37:03Operational experience
related talks
37mTesting in a Microservices Architecture
53mTinkertoys, microservices, and feature management: How to build for the future
47mBreak Up the Monolith: Testing Microservices
08mTesting Microservices
27mTinkertoys, Microservices, and Feature Management: How to Build for the Future
35mMicroservice Testing
57mEnd-to-End Automated Testing in a Microservices Architecture
52mTesting Microservices
