Testing · 01 of 03 · The model

How Testkube runs a test

A test is a resource, like a Deployment. The open source agent runs it in your cluster, in whatever framework the test already uses, and the control plane is where you see every run in one place.

How Testkube runs a test Three rows. What starts a run: a CI pipeline (Tekton, GitHub Actions, Jenkins), the CLI or API (testkube run testworkflow), a schedule declared in the workflow, or a Kubernetes event through a TestTrigger. All four start a TestWorkflow, highlighted, which is a Kubernetes resource kept in git. The open source Testkube agent, running in your cluster, runs it, fanning out to three workers, each one shard of three, labelled parallel, shards and matrix. The workers produce results and artifacts: logs, reports and step status. Those go to an optional control plane, a dashboard in the cloud or on-premises, drawn dashed because it is the optional, commercial part, and out as notifications through webhooks and CDEvents. WHAT STARTS A RUNIN YOUR CLUSTER · THE AGENTWHERE THE RESULTS GOCI pipelineTekton · Actions · JenkinsCLI or APItestkube run testworkflowA schedulecron, in the workflowKubernetes eventa TestTrigger on a resourceRUNSTestWorkflowa Kubernetes resource, in gitTestkube agentopen source · in your clusterWorker 1 · shard 1 of 3Worker 2 · shard 2 of 3Worker 3 · shard 3 of 3PARALLEL · SHARDS · MATRIXResults and artifactslogs · reports · step statusControl planedashboard · cloud or on-premNotificationswebhooks · CDEventsYour tests, in any framework, declared once and run where your apps run.LEGENDWho starts itThe declared testWhat it producesOptional, commercialRunsReports

Declared, not scripted

A TestWorkflow says which image, which steps, which services and which artifacts to keep. It lives in git and gets reviewed like anything else.

Bring your framework

k6, Playwright, Cypress, JMeter, Postman, pytest: if it runs in a container, Testkube can orchestrate it. Nobody rewrites a test suite to adopt it.

Free agent, optional pane

The agent is open source and runs standalone. The dashboard that gathers every run lives in the commercial control plane, hosted or on-premises.

Hangar · Glidepath · Testing