Who broke the build? Use Kuttl to improve E2E tests
summary
KUTTL provides a YAML declarative framework to run end-to-end tests locally using KUTTL, kind (via startKind: true), Docker Desktop and kubectl, producing XML/JSON reports that integrate with CI. The demo runs four parallel tests, asserts state like replicas=1, times out tests after 300s, and cleans up namespaces on success. The claim is that reproducing CI test environments locally cuts remote round trips, reduces broken builds and speeds merges by letting developers fix failures before pushing.
AI-written summary · about
chapters (30)
- 0:00intro
- 0:27preamble
- 1:16about ram mohan
- 1:50jfrog in a slide
- 2:37everything runs on software
- 3:14software updates matter
- 3:47jfrog's mission
- 4:04fast adoption by enterprises
- 4:21the ecosystem
- 4:33software delivery has evolved
- 6:18agenda
- 7:25ideal development environment
- 7:55easy setup
- 8:32benefits
- 9:01equivalent
- 9:13steps to merge a pull request
- 10:55remote e2e tests
- 11:38local e2e tests
- 13:24kuttl
- 14:25kubernetes test tool - benefits
- 15:36get started
- 16:32kuttl is for you if
- 17:15test suite configuration
- 19:15test step
- 20:04test step assert
- 20:32test suite structure
- 21:01demo
- 29:58references
- 30:23summary
- 31:02questions?
related talks
35mWho Broke the Build? — Using Kuttl to Improve E2E Testing and Release Faster
34mWho broke the build—Using Kuttl to improve E2E testing and release faster
33mWho broke the build? Using Kuttl to test and Release faster
26mWho broke the build? Using Kuttl to release fast
27mDeclarative Testing Clusters with KUTTL
36mEfficient Kubernetes E2E Testing: Unleash the Power of Prow
28mAre You Covered? Falling in Love With E2E Testing
34mBreaking the Build Before It Breaks You: The Magic of E2E Tests