Glossary

A backup of persistent storage. Useful for preserving test environments or artifacts.

Persistent storage for Kubernetes workloads. Testkube may use persistent volumes to save test artifacts.

Pushing systems beyond normal limits to find breaking points. Testkube orchestrates stress tests in Kubernetes environments.

A predefined structure for creating resources. Testkube may use templates for test manifests or pipelines.

An infrastructure-as-code tool for provisioning resources. Testkube can be deployed using Terraform scripts.

Metrics and insights generated from test executions to help teams identify trends, flaky tests, and performance issues. Testkube provides analytics across test runs and environments.

Files or data generated as a result of running a test, such as logs, screenshots, or performance reports. Testkube stores and manages test artifacts for analysis and debugging.

A defined scenario specifying inputs, actions, and expected outcomes. Testkube executes test cases via its orchestrated workflows.

Data used as input for tests. Testkube can manage test data through config maps, secrets, or Git resources.

Creating, masking, and managing realistic test data while protecting sensitive production information. Testkube handles configs and secrets injection into test pods, but full test data virtualization is outside its scope.

The process of automatically identifying test definitions across repositories or infrastructure. Testkube supports discovering tests defined in Git repos or clusters.

A component in Testkube responsible for running a specific type of test, such as Postman collections, k6 scripts, or Selenium tests, inside Kubernetes environments.

Selecting and executing only the tests affected by code changes to accelerate pipelines and feedback.

The process of coordinating when, where, and how tests run across environments, tools, and infrastructure. Testkube acts as a test orchestration platform for Kubernetes, managing and automating complex testing workflows.

The practice of defining tests in a way that they can be run across multiple environments, configurations, or pipelines. Testkube supports reusable test definitions stored in version control.

A single execution of a test in Testkube, capturing results, logs, artifacts, and any failures.

Running automated tests on a defined schedule, such as nightly builds or recurring pipeline triggers. Testkube supports cron-like scheduling inside Kubernetes for recurring test runs.

A sequence of actions defining how tests are triggered, executed, and reported in Testkube. Workflows integrate with CI/CD pipelines and external tools.

A credential used for authentication. Testkube uses tokens for secure API and Git integrations.

An event that starts a process, like running a test. Testkube supports triggers from CI/CD tools, webhooks, or schedules.

Verifying individual components or functions in isolation to ensure correctness before integration.

Checking whether results meet expectations. Testkube validates test outcomes automatically.

A placeholder for values that can change. Testkube supports variables in test configurations.

Systems for tracking changes to code and files. Testkube relies on version control for managing test definitions and configurations.

A storage resource mounted into pods. Testkube may use volumes for test result storage.

An HTTP callback triggered by events. Testkube can use webhooks to start test runs from external systems.

A defined series of steps to accomplish tasks like testing or deployment. Testkube manages workflows for test orchestration.

A load testing tool for measuring API performance. Testkube can run k6 tests in Kubernetes environments.