Website |  Documentation |  Changelog |  Blog |  Slack |  LinkedIn |  X

Welcome to Testkube!

Testkube is a Test Orchestration Platform for Cloud-Native Applications. It provides a single platform for defining, running and analyzing test executions, using your existing testing tools/scripts, running in your existing infrastructure.

Testkube consists of a Control Plane and any number of Testkube Agents. The Control Plane exposes a Dashboard for easy and centralized access to most Testkube features.

The Testkube Agent (this repo) is 100% Open-Source and can be deployed standalone without a Control Plane - Read More.

Why use Testkube?

• Run any Tests : Execute any tests/tools/scripts at scale; API, E2E, Performance, Security, Infrastructure, etc. - Examples & Guides.
• Trigger Tests whenever needed: Trigger tests manually, on schedules, from CI/CD/GitOps pipelines, on Kubernetes Events, via the REST API, through MCP, etc. - Read More.
• Results and Analytics: All test results, artifacts, logs and resource-metrics are aggregated for centralized troubleshooting and reporting - Read More.
• Works with your tools: Integrate with existing tools and infrastructure using Webhooks, the Testkube REST API or the MCP Server - see Integration Examples.
• AI Agents: Build AI Agents for troubleshooting, analysis, remediation, etc - Read More
• Enterprise Ready: SSO/SCIM, RBAC, Teams, Resource-Groups, Audit-logs, etc. - Read More.

Getting Started with Testkube Open Source

To get started with the open source agent:

• The Helm or CLI Installation will make it easy to deploy the agent into your target cluster.
• The Quickstart is the easiest way to set up Testkube and run your first tests.

Check out the Testkube Open Source Overview to learn more about the open source deployment architecture.

Getting Started with the Commercial Control Plane

Looking for more than single environment test execution? Do you need orchestration accross clusters, support for different trigger points, and high level reporting and artifact collection? Enterprise may be for your team - there are several ways to get started:

• The Quickstart is the easiest way to set up Testkube and run your first tests
• The Helm Chart Installation gives you more control over the installed components.
• The Feature Comparison page details the differences between Enterprise and Open Source.

Check out the Installation Overview to learn more about different ways to deploy and run the Testkube Control Plane.

Documentation

Extensive documentation is available at docs.testkube.io.

Contributing

Check out our Contributors Guide and the Agent Architecture to find your way around our codebase and process.

If you want to contribute code, this reading order works well:

1. CONTRIBUTING.md - contribution workflow, coding standards, and PR process
2. DEVELOPMENT.md - local setup with Tilt and day-to-day development loop
3. ARCHITECTURE.md - high-level system design and key code paths

Shout-out to our contributors 🎉 - you're great!

• ⭐️ @lreimer - K6 executor Gradle executor Maven executor
• ⭐️ @jdborneman-terminus - Ginkgo executor
• ️⭐️ @abhishek9686
• ⭐️ @ancosma
• ⭐️ @Stupremee
• ⭐️ @artem-zherdiev-ingio
• ⭐️ @chooco13 - Playwright executor

Go to contribution document to read more how can you help us 🔥

Feedback

Whether Testkube helps you or not, we would love to help and hear from you. Please join us on Slack to ask questions and let us know how we can make Testkube even better!