Given the operator nature, we rely heavily on integration and end-to-end (e2e) tests.
E2E tests are built with shell scripts. They are mainly POSIX-compliant scripts (the only exception is the use of local variables in functions).
The easiest way to run the e2e scripts is by executing the
This will configure a Kubernetes cluster (by default using kind), build the JVM version of the operator, and deploy it to the configured Kubernetes cluster.
The E2E tests are grouped by specifications, which are located in the
There are also several util functions, which are located in the
For more information, have look at the E2E readme.
By default, e2e tests use kind to create and configure a Kubernetes cluster, so you don’t need to specify anything other than having kind installed.
The Kubernetes environment can be specified using the
E2E_ENV environment variable. Currently we support the following environments: