Skip to content


Unit and integration tests

Unit and integration tests can be run using go test

To run all tests:

go test -v ./...

Adding an integration test

The integration tests takes a cluster spec and builds cloudformation/terraform templates. For new functionality, consider adding it to the cluster unless it conflicts with existing functionality in that cluster. To add a new integration test, create a new directory in tests/integration/update_cluster/ and put the cluster spec in in-v1alpha2.yaml. Use a unique cluster name.

Then edit ./cmd/kops/integration_test.go and add the test function with the cluster name and directory from above.

Lastly run ./hack/ to generate the expected output.

Kubernetes e2e testing

Preparing the environment

The easiest way to run the Kubernetes e2e tests is to install the kubetest binary from test-infra.

See e2e-tests for instructions how to install and general usage of the utility.

You can see the various jobs that are periodically run against kops. The container arguments for each of the jobs are the ones passed to kubetest.

Following the examples below, kubetest will download artifacts such as a given Kubernetes build. Therefore you probably want to run kubetest from a directory dedicated for this purpose.

Running against an existing cluster

You can run something like the following to have kubetest re-use an existing cluster. This assumes you have already built the kOps binary from source. The exact path to the kops binary used in the --kops flag may differ.

GINKGO_PARALLEL=y kubetest --test --test_args="--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[HPA\]|Dashboard|Services.*functioning.*NodePort" --provider=aws --deployment=kops --kops-state=${KOPS_STATE_STORE} --kops ${GOPATH}/bin/kops --extract=ci/latest

Note the --extract flag is only needed on first run or whenever you want to update the kubernetes build. You can omit this flag to run against the already extracted tree on subsequent runs. Just cd into the kubernetes directory first.

Running against a new cluster

By adding the --up flag, kubetest will spin up a new cluster. In most cases, you also need to add a few additional flags. See kubetest --help 2>&1 | grep kops for the full list.

GINKGO_PARALLEL=y kubetest --test --test_args="--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[HPA\]|Dashboard|Services.*functioning.*NodePort" --provider=aws --check-version-skew=false --deployment=kops --kops-state=${KOPS_STATE_STORE} --kops ${GOPATH}/bin/kops --kops-args="--network-cidr=" --up --kops-ssh-key ~/.ssh/id_rsa --kops-admin-access=

If you want to run the tests against your development version of kOps, you need to upload the binaries and set the environment variables as described in Adding a new feature.

Since we assume you are using this cluster for testing, we leave the cluster running after the tests have finished so that you can inspect the nodes if anything unexpected happens. If you do not need this, you can add the --down flag. Otherwise, just delete the cluster as any other cluster: kops delete cluster --yes