The Artillery executor allows you to run Artillery tests with Testkube.
Testkube is able to run cURL commands as tests.
Our dedicated Cypress executor allows running Cypress tests with Testkube - directly from your Git repository.
Our dedicated Ginkgo executor allows running Ginkgo tests with Testkube - directly from your Git repository.
Testkube allows running Gradle based tasks that could also be tests. For example, we can easily run JUnit tests in Testkube.
JMeter is an integral part of Testkube. The Testkube JMeter executor is installed by default during the Testkube installation.
Testkube's k6 executor provides a convenient way of running k6 tests.
KubePug is a kubectl plugin checking for deprecated Kubernetes clusters or deprecated versions of Kubernetes manifests. It can connect to both your cluster directly and it can run on input files.
Testkube allows you to run Maven-based tasks which could be also tests. For example, we can easily run JUnit tests in Testkube now.
Starting from the Testkube Helm chart version 1.9.5, it is possible to use Testkube to manage your Playwright tests inside your Kubernetes cluster.
Testkube is able to run Postman collections inside your Kubernetes cluster so it can be used to test internal or external services.
SoapUI is an open-source tool used for the end-to-end testing of REST, SOAP and GraphQL APIs, as well as JMS, JDBC and other web services. Testkube supports the SoapUI executor implementation.
Testkube supports running trace-based tests with Tracetest.
OWASP Zed Attack Proxy Executor
Starting from version 1.12, Testkube has a dedicated executor for running ZAP tests. All you need to do is populate a file with the necessary parameters and create a Testkube test.
📄️ Prebuilt Testkube Executor
The new and recommended way of running custom images is to use Container Executors.
📄️ Container Executor
The Testkube Container Executor allows you to run your own container images for executing tests. Testkube orchestrates the Tests using the container image as Kubernetes Jobs.