Why Kubernetes Applications Require a New Approach to Testing using Testkube
summary
Testkube runs tests in-cluster as tests as Kubernetes CRDs, decoupling test orchestration from CI/CD and replacing heavy pipeline scripting with a Kubernetes operator that schedules executors, gathers logs and artifacts (videos from Cypress, k6 output), and emits metrics and webhooks. It supports k6, Cypress, Postman, SoapUI and custom executors, runs tests in parallel (demo launches 26 k6 jobs causing intermittent failures), stores history and artifacts, triggers on cluster events, and is shipping features like timeouts in v1.7.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:21Challenges of testing in Kubernetes
- 4:57Cloud native testing principles
- 7:02Introducing Testkube
- 9:33Simplifying test pipelines with CRDs
- 11:22Live demo of Testkube
- 17:30Q&A session
related talks
16mWhy Kubernetes Applications Require a New Approach to Testing using Testkube- 16mWhy Kubernetes Applications Require a New Approach to Testing using Testkube
33mThe Power of a Unified Testing Approach in Kubernetes
33mTake Your Tests to the Cloud with Testkube
32mRedefining Continuous Testing in Kubernetes Environments
45mMario Leander Reimer: K8s-native Quality Assurance of Microservices with Testkube
56mQuality in a Square K8s-native Quality Assurance of Microservices w. Testkube
35mIntro: Testing SIG