Glossary

Validating APIs for correctness and performance. Testkube runs API tests with tools like Postman or REST Assured.

Metadata attached to Kubernetes objects for storing additional information. Testkube may use annotations for test configuration or tracking.

Software running in an environment. Testkube tests applications deployed in Kubernetes.

A GitOps tool for Kubernetes deployments. Testkube can be deployed and managed via ArgoCD.

A file generated during builds or tests, like logs or reports. Testkube stores test artifacts for analysis.

A load testing tool for APIs and services. Testkube can run Artillery scripts in Kubernetes environments.

A statement that verifies expected results in a test. Testkube captures assertion results in test reports.

A Git hosting platform. Testkube supports Bitbucket repositories for managing test definitions.

Connecting Testkube into continuous integration and deployment pipelines so tests run automatically on code changes or deployments.

A CI/CD service. Testkube can integrate with CircleCI to run tests in Kubernetes.

A collection of machines running Kubernetes workloads. Testkube deploys executors and test pods into clusters to run tests.

A text-based interface for running commands. Testkube offers a CLI to manage tests and workflows.

Stores configuration data in Kubernetes. Testkube can read config values from ConfigMaps for test executions.

Settings that define how software behaves. Testkube uses configurations to customize test executions.

A lightweight, standalone executable package containing an application and its dependencies. Testkube uses containers to package and run test executors.

A snapshot of a container’s contents, used to launch containers consistently. Testkube stores and pulls container images to run test executors.

A metric showing how much code is tested. Testkube can aggregate coverage reports from test executions.

A user-defined executor in Testkube that allows running tests using custom logic or tools not provided out-of-the-box.

A tool for end-to-end web testing. Testkube supports running Cypress tests in clusters.

A Kubernetes object that ensures the desired number of pod replicas are running. Testkube executors are usually deployed via Kubernetes deployments.

Executing tests across multiple machines or Kubernetes nodes for scalability. Testkube supports distributed testing by orchestrating workloads across clusters.

A platform for building and running containers. Testkube uses Docker images for test executors.

Testing entire workflows as a user would experience them. Testkube executes E2E tests across Kubernetes clusters.

A context where software runs, such as dev, staging, or production. Testkube executes tests across multiple environments.

A short-lived testing environment created on demand, often spun up in Kubernetes for each test run or pipeline. Testkube supports ephemeral test environments for isolated, clean tests.

An issue causing test failure. Testkube logs errors for troubleshooting.

A record of something happening in the Kubernetes system. Testkube events can help trace test execution issues.

The runtime context where a test executes, including environment variables, secrets, and configurations. Testkube isolates tests into separate Kubernetes pods for clean execution environments.

A test result indicating the system didn’t behave as expected. Testkube highlights failures in analytics.

Tests that sometimes pass and sometimes fail without any code changes, often due to timing, dependencies, or unstable environments. Testkube helps identify flaky tests through centralized analytics.

Testing specific features for correct behavior. Testkube supports functional testing across environments.

A version control system for tracking changes in code. Testkube integrates with Git for managing test definitions and GitOps workflows.

A platform for Git repositories and workflows. Testkube integrates with GitHub Actions and GitHub-hosted repos.

A DevOps platform with Git repositories and CI/CD. Testkube integrates into GitLab pipelines for test orchestration.

A methodology where infrastructure and applications are managed via Git repositories as the source of truth. Testkube supports GitOps by versioning test configurations in Git.

A visualization platform for metrics and logs. Testkube data can be displayed in Grafana dashboards.

A tool for managing Kubernetes applications using packaged charts. Testkube can be installed via Helm for simplified deployment.

A process triggered at specific points in a lifecycle, like pre- or post-test execution. Testkube supports hooks to customize workflows.

A unique label for a resource. Testkube assigns identifiers to tests and runs for tracking.

Defining infrastructure using code. Testkube integrates into IaC workflows by deploying via manifests or Helm charts.

Manages external access to services in Kubernetes. Testkube can be exposed via ingress rules.

Connecting tools and systems. Testkube integrates with CI/CD pipelines, test frameworks, and observability tools.

Verifying how multiple components work together. Testkube runs integration tests as part of workflows.

A tool for load and performance testing. Testkube can run JMeter tests in Kubernetes for large-scale performance testing.

An automation server used for building, testing, and deploying applications. Testkube can integrate with Jenkins pipelines or replace certain testing functions.

A single unit of work in CI/CD tools. Testkube creates jobs in Kubernetes to execute tests.

An open-source platform for automating deployment, scaling, and management of containerized applications. Testkube runs tests directly inside Kubernetes for scalable, native execution.

Running tests directly inside Kubernetes clusters instead of external machines or cloud services. Testkube specializes in Kubernetes-native testing orchestration.

Key-value pairs attached to Kubernetes resources for identification and filtering. Testkube uses labels to track and manage test executions.

Testing a system’s performance under high user load. Testkube supports load testing tools like k6 or JMeter in Kubernetes.

A YAML or JSON file defining Kubernetes resources like deployments or services. Testkube deployments and executors are often described using manifests.

Associating one value to another. Testkube mappings may define test configurations or secrets.

Numerical data that measure performance or outcomes. Testkube aggregates metrics from test runs for analysis.

Simulating dependencies to isolate tests. Testkube supports tests that rely on mocked services.

Running workloads across multiple Kubernetes clusters. Testkube supports multi-cluster test orchestration for enterprise scalability.

A way to group Kubernetes resources for isolation and organization. Testkube can run tests in specific namespaces for better management.

A physical or virtual machine in a Kubernetes cluster that runs pods. Testkube utilizes nodes to distribute test workloads.

The ability to understand what’s happening inside systems based on logs, metrics, and traces. Testkube enhances observability for tests by capturing logs, metrics, and results across all executions.

Running multiple tests at the same time to speed up testing. Testkube leverages Kubernetes scalability to run tests in parallel across pods and clusters.

A value provided to customize a process. Testkube uses parameters for test inputs.

Assessing system speed and stability. Testkube enables performance tests directly in Kubernetes clusters.

A sequence of automated steps in software delivery, such as building, testing, and deploying. Testkube integrates into pipelines for automated testing.

A modern browser testing framework. Testkube can execute Playwright tests in Kubernetes.

The smallest deployable unit in Kubernetes, containing one or more containers. Testkube runs each test in its own pod for isolation and scalability.

A tool for building and running API tests. Testkube integrates with Postman collections to execute API tests natively in Kubernetes.

A monitoring and metrics collection system. Testkube integrates with Prometheus for test metrics.

Setting up infrastructure automatically. Testkube provisioning involves deploying its components into Kubernetes clusters.

A Java-based API testing library. Testkube can orchestrate REST Assured tests in Kubernetes.

Ensuring new changes don’t break existing features. Testkube orchestrates regression tests automatically in pipelines.

A summary of test results. Testkube generates reports with logs, artifacts, and metrics.

A place to store code, configurations, or test definitions. Testkube can read tests from Git repositories.

An object managed by Kubernetes, such as pods, services, or secrets. Testkube creates resources like pods and jobs for test executions.

The outcome of a test run: pass, fail, or error. Testkube captures results centrally.

Adjusting resources up or down. Testkube leverages Kubernetes scaling for parallel or high-volume test execution.

A file containing a series of commands. Testkube can execute test scripts stored as artifacts or Git resources.

A Kubernetes object for storing sensitive information like passwords. Testkube injects secrets into test pods securely.

Safely handling sensitive data like API keys, tokens, or passwords. Testkube integrates with Kubernetes Secrets to securely inject secrets into test executions.

A framework for automating browser tests. Testkube runs Selenium tests in Kubernetes for scalable UI testing.

A stable endpoint that routes traffic to pods in Kubernetes. Testkube may expose test results or APIs via services.

A command-line interpreter used to execute commands. Testkube’s CLI operates in shell environments.

Basic tests to check if a system is stable enough for deeper testing. Testkube supports smoke test orchestration.

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.

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.

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.

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.

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

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