Skip to content

testing.md

Latest commit

 

History

History
34 lines (25 loc) · 1.38 KB

testing.md

File metadata and controls

34 lines (25 loc) · 1.38 KB

Integration Tests

Infrastructure

The infraflow code path of the infrastructure controller contains nearly no unit tests, as it primarily consists of code interacting with the STACKIT IaaS API. Instead, these code paths are tested via the infrastructure integration tests.

To run them, set the environment variables below and run make test-integration-infra.

export STACKIT_PROJECT_ID=<PROJECT_ID>
export STACKIT_SERVICE_ACCOUNT_KEY=$(pbpaste)
make test-integration-infra

The STACKIT_SERVICE_ACCOUNT_KEY is simply the JSON struct obtained from the Portal or API, when creating a new Service-Account key. Additionally the ServiceAccount also needs to have the iaas.network.admin as well as the iaas.isolated-network.admin roles in-order to create all necessary resources via the API.

SelfHostedShootExposure

The selfhostedshootexposure controller provisions an NLB through the STACKIT Network Load Balancer API. Run the integration tests via:

export STACKIT_PROJECT_ID=<PROJECT_ID>
export STACKIT_SERVICE_ACCOUNT_KEY=$(pbpaste)
make test-integration-exposure

The ServiceAccount needs the same level of access as the infra tests (it provisions an isolated network used as the LB's target network) plus permissions to create/update/delete STACKIT load balancers. In practice, the owner role on the project (or a parent folder) covers everything the suite does.