Who Broke the Build? — Using Kuttl to Improve E2E Testing and Release Faster
summary
A practical report on replacing slow remote E2E runs with Kuttl: teams convert Helm-chart and Artifactory stack tests into YAML testSuites (testSteps + assertions), run them locally on Kind or a vcluster with cached images, and get XML/JSON reports. Parallelism runs parallel eight tests, bringing full-suite time from hours to 15 minutes in one case. Tests launch namespaces automatically, reproduce failures via copied commands, and cut main-branch build breaks significantly. Tools: Kuttl, vcluster.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:05End-to-end testing pain points
- 3:57CI/CD workflow challenges
- 6:29Kuttl for local testing
- 7:15What is Kuttl
- 8:42Kuttl setup
- 13:20Live demo: Kuttl
- 18:42Kuttl vs Chart Testing
- 21:13Kuttl assertions
- 24:50Benefits of Kuttl
- 25:42Q&A on app changes
- 29:31Summary and references
- 30:36Impact on build breaks
- 31:02Q&A on Chainsaw
related talks
23mBeyond unit tests: Contributing high level tests for Amazon ECS
31mContributing to KernelCI for Better Testing and Collaboration
35mFork It Harder Make It Better
20mAdopting Bazel in a quickly scaling organization
14mUsing packit and testing farm for CI/CD and automation in an upstream project
50mDo our development tools need a refresh?
37mFork It Harder Make It Better
22mCreating a Micro Open-Source Community with Helm