The AI Kubernetes Show

Treat Testing as a Platform Service on Kubernetes

48 min · I går
episode Treat Testing as a Platform Service on Kubernetes cover

Beskrivelse

Most testing tools bolt onto a CI pipeline and hope for the best. Ole Lensmar, CTO of Testkube, built a company that changes that script. Pull test execution out of CI/CD entirely and run tests as Kubernetes workloads instead. In this episode, Lensmar walks through why Testkube uses Kubernetes as its test execution engine, running Selenium, Playwright, K6, JMeter, and Postman tests as cluster workloads instead of asking teams to adopt new tools. He and podcast host William Morgan dig into who should own testing (developers own functional tests,  while the platform team owns performance, security, and chaos testing). Lensmar's core recommendation is to treat testing and quality as a platform capability, the same way you already treat CI and CD.  More AI-generated code means more tests are needed, intelligent test selection can keep pipelines fast as test counts grow, and AI is already useful for triaging failed test logs using Kubernetes and Grafana MCP servers.   TAKEAWAYS:  ✓ Where testing ownership splits between developers and the platform team, and where it doesn't  ✓ Why "testing as a platform service" should get the same priority as CI and CD  ✓ How intelligent test selection works, and why you should never rely on it alone  ✓ Where AI already adds value today: triaging failed test logs with Kubernetes and Grafana MCP servers  ✓ Why testing the AI components of your application (agents, evals) is becoming its own discipline. Read the blog post at:

Kommentarer

0

Vær den første til å kommentere

Registrer deg nå og bli medlem av The AI Kubernetes Show sitt community!

Prøv gratis

Prøv gratis i 14 dager

99 kr / Måned etter prøveperioden. · Avslutt når som helst.

  • Eksklusive podkaster
  • 20 timer lydbøker i måneden
  • Gratis podkaster

Alle episoder

25 Episoder

episode Treat Testing as a Platform Service on Kubernetes cover

Treat Testing as a Platform Service on Kubernetes

Most testing tools bolt onto a CI pipeline and hope for the best. Ole Lensmar, CTO of Testkube, built a company that changes that script. Pull test execution out of CI/CD entirely and run tests as Kubernetes workloads instead. In this episode, Lensmar walks through why Testkube uses Kubernetes as its test execution engine, running Selenium, Playwright, K6, JMeter, and Postman tests as cluster workloads instead of asking teams to adopt new tools. He and podcast host William Morgan dig into who should own testing (developers own functional tests,  while the platform team owns performance, security, and chaos testing). Lensmar's core recommendation is to treat testing and quality as a platform capability, the same way you already treat CI and CD.  More AI-generated code means more tests are needed, intelligent test selection can keep pipelines fast as test counts grow, and AI is already useful for triaging failed test logs using Kubernetes and Grafana MCP servers.   TAKEAWAYS:  ✓ Where testing ownership splits between developers and the platform team, and where it doesn't  ✓ Why "testing as a platform service" should get the same priority as CI and CD  ✓ How intelligent test selection works, and why you should never rely on it alone  ✓ Where AI already adds value today: triaging failed test logs with Kubernetes and Grafana MCP servers  ✓ Why testing the AI components of your application (agents, evals) is becoming its own discipline. Read the blog post at:

I går48 min