Strategies for Testing Your Pipeline
summary
Advocates replacing fragile Bash steps with a language that has unit tests, using Go to compile and package tested tools into task images, and building a small framework that deploys and validates on a test Kubernetes cluster to assert resource status and labels. Emphasizes replace long Bash scripts with Go unit-tested programs for network, parsing, or dependency checks, runs nightly end-to-end pipeline checks to catch external drift, and prioritizes thorough testing of deploy stages over simple clone/build steps.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:24Another Example
- 4:25Language with testing
- 7:44Using a framework
- 8:47What is the framework
- 10:54Integration tests
- 15:11Recap
related talks
31mWho Tests the Testers? Making and Testing Pipelines
22mLet's Build A CI CD Pipeline
39mRemove your Testing Bottleneck with CI/CD Pipelines
27mExploring a DevOps Transformation Like a Tester
25mHow NOT to Build a Pipeline
26mThe Impact of Testing on a DevOps Pipeline
44mThe Pipeline Driven Organization｜
39mModern Data Pipelines Testing Techniques: A Visual Guide