Kubernetes Test Execution

RobusTest can use Kubernetes to provision test execution containers on demand. This allows you to run tests against virtual device or browser environments in a Kubernetes cluster rather than (or in addition to) physical devices.

Overview

A Kubernetes configuration in RobusTest defines the container image to use for a given OS and OS version combination. When a job is created that targets that OS version, RobusTest spins up the configured container in the cluster.

The Kubernetes cluster connection is configured by your RobusTest administrator in the platform config (kubernetesConfig.configPath).

Managing Kubernetes Configurations

List all configurations

GET /v3/kubernative/all

Returns all registered Kubernetes execution configurations.

Create a configuration

POST /v3/kubernative/:id

The :id is a new ID placeholder — pass any valid ObjectId string.

Request body:

{
  "os": "android",
  "osVersion": "12",
  "image": "registry.example.com/android-emulator:12",
  "desc": "Android 12 emulator image"
}

Field	Description
`os`	Target platform: `android`, `ios`
`osVersion`	OS version string (e.g. `12`, `14.5`)
`image`	Full Docker image reference including registry and tag
`desc`	Optional description

Delete a configuration

DELETE /v3/kubernative/:id

Using Kubernetes in a Job

When creating a job, RobusTest automatically matches the target OS and version against registered Kubernetes configurations. If a match is found and no physical device is available, RobusTest launches the container image to fulfil the test execution.

No additional job payload changes are required — device targeting works the same way as with physical devices.

Admin Console