Testing

July 24, 2026 ยท View on GitHub

Running the tests

Unit Tests

To run the node-local unit tests, run:

make test-unit

E2E Tests

To run the e2e tests against a custom-setup, special-purpose kind cluster, just run:

make test-e2e-kind

Set the environment variable DRACPU_E2E_VERBOSE to 1 for more output:

DRACPU_E2E_VERBOSE=1 make test-e2e-kind

In some cases, you may need to set explicitly the KUBECONFIG path:

KUBECONFIG=${HOME}/.kube/config DRACPU_E2E_VERBOSE=1 make test-e2e-kind

The test-e2e-kind will exercise the same flows which are run on the project CI. The full documentation for all the supported environment variables is found in the tests README.

NOTE: the custom-setup kind cluster is not automatically torn down once the tests terminate. NOTE: if you want to run the tests again on the existing kind cluster, just use make test-e2e. Please see make help for more details.

Testing Local Changes in a Kind Cluster

The simplest way to build the driver from source and deploy it into a new Kind cluster is using:

make ci-kind-setup

This command builds the driver image, creates a Kind cluster, loads the image, and installs the driver manifests in grouped mode (the default).

To install the driver in individual mode instead, use:

DRACPU_E2E_CPU_DEVICE_MODE=individual make ci-kind-setup

To clean up the environment when finished, run:

make delete-kind-cluster