Conf in a Conf Session

Why Kubernetes Apps Require a New Approach to Testing

25-minute Talk

Advanced session

Timetable

12:00 a.m.-12:30 a.m.

Wednesday 15th

Room

Track 3

Audience

This talk is aimed for teams of developers, operations and QA testers.

Key-Learning

- Running tests inside the cluster simplifies DevOps efforts.

- Using Kubernetes-native abstraction enables the use of GitOps practices with testing.

- Having a common format of results for different testing types improves testing observability.

Tooling focused on testing hasn't caught up in the Cloud Native ecosystem. Complex CI/CD pipelines get in the way of achieving a culture of speed and resilience for DevOps teams. Let's solve that!

Microservices, CI/CD, DevOps, GitOps, cluster networking, etc — more and more teams are building software fundamentally differently than they did even a few years ago. However, testing approaches and tooling have not caught up yet. At least not until now.

What if you could apply the same type of GitOps and DevOps methodologies to your testing activities? Tests could be deployed and stored in a Kubernetes cluster, they could decoupled from your CI/CD, orchestrated in the cluster in the same way you do with your applications and not in your CI/CD, publish results aggregated in a common format and triggered with a simple API request. Looks promising right?

Let’s have a look at Testkube, an open-source framework that is moving to be the cloud-native testing framework for all your Tests in Kubernetes. Whether you are using Postman, Cypress, K6, SoapUI, or any other testing tool, Testkube can unlock all the capabilities of those tools that allow you to deliver code with confidence.