Features

Leverage K8s for Testing

Tests as Custom Resources

With Testkube, tests are defined as a Kubernetes Custom Resource. This means you have full flexibility on how the execution of the test will happen by adding labels, annotations and expanding commands and arguments.

Kubernetes Jobs to scale your tests

Every test execution is created as a Kubernetes Job, allowing you to schedule executions and scale to as many test executions needed. Testkube scales with your Kubernetes scaling powers!

GitOps Friendly

Since Testkube manages key artifacts (tests, testsuites, etc) as CRDs, it works nicely with a GitOps approach to managing your cluster state. Tools like ArgoCD and Flux can ensure the right tests are deployed to your cluster, while also running Testkube tests to validate the state of your cluster after reconciliation.

Get Started

Create a Platform for Testing

Testkube helps you build a platform for testing that enables teams in your organization to easily create tests without dependencies with other teams, getting better observability on the state of testing and improve debugging of failed tests.

Testkube Dashboard

In the Testkube Dashboard you have better observability on how tests are working across your organization. Create tests, run them, debug them and delete them just with a couple of clicks.

Consistent Test Results

Testkube runs any testing tool your are currently using. Now you can have a centralized place where all the tools are reporting logs and artifacts. Goodbye to test results that are spread across multiple places.

Get Started

Start either in the Cloud or Self-host

Cloud

Managed Testkube with everything in Open Source + multi-cluster support, environments, and user roles.

Try Cloud for Free
Open Source

Try the self-managed version and start your journey of testing Kubernetes applications effortlessly.

Download
What’s the Difference?

Run Tests Inside your Cluster

Run your tests securely

With Testkube, all your tests are run directly inside your cluster as a Kubernetes Job. This means that you don’t need to expose your micro-services or give your CI servers (or testers) access to your cluster just for testing purposes. Run your tests in an air-gapped fashion and save yourself from supply chain attacks.

Cluster-related Triggers

As Testkube is installed inside your Kubernetes cluster, it can listen to cluster events (for example, a Deployment object has been updated) and trigger tests based on that. Say hello to running tests whenever and however you need!

Watch our guide on using Testkube Test Triggers

Get Started

Break Free from Testing Constraints

Run Tests Whenever and However you want

Testkube enables you to run tests in multiple ways for maximum flexibility using either:

Testkube Dashboard

Testkube CLI

Triggering on Kubernetes Cluster Events

From any CI/CD Pipeline

Through the Testkube REST API

On Cron Jobs

... and more!

Integrate with existing tools and pipelines

Get Started
Thanks to Testkubes REST API and support for CDEvents it is easily integrated into any CI/CD pipelines already deployed in your organisation, making sure that testing is performed at every step of your application lifecycle.