Dev/Testing challenges with microservices and CD
summary
Built a test harness that wraps native go testing cases into containerized pods on OpenShift using the operator framework, letting the same tests serve pre-merge, post-merge, monitoring and smoke roles. Tests carry arbitrary labels, run in parallel by width/depth (example: width 4 depth 5 = 20 executions saved), record elapsed times and error strings into JSON on the test object (configMap/Status), and forward errors to entry. The system runs the pods, persists results, and enables automated promotion decisions from stage to prod.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:12Agenda
- 2:26Prototyping
- 6:54Continuous Deployments
- 8:44Should Developers Take Over Testing
- 11:03Code Quality Guidelines and Best Practices
- 11:42Code Format
- 12:18Code Reviews and Test Execution
- 13:11Automation Testing
- 13:59Production Testing and Monitoring
- 14:58Monitoring
- 19:44Backwards Compatibility
- 24:12Achieve Continuous Deployments and Automated Promotion
- 27:34Testing Challenges
related talks
57mComprehensive testing strategies for modern microservice architectures
47mInfrastructure under Test in OpenShift
35mDynamically Testing Individual Microservice Releases In Production
28mContinuous Integration Testing: Fully Test your Microservices Application, Early and Often
40mBoosting test coverage for microservices
30mTestOps: Transforming Chaos into Streamlined Story-Based Releases
57mEnd-to-End Automated Testing in a Microservices Architecture
06mIntegration Testing with TestContainers-Go