Skip to content

Latest commit

 

History

History
22 lines (16 loc) · 659 Bytes

README.md

File metadata and controls

22 lines (16 loc) · 659 Bytes

Locally running e2e test suite

When updating your operator it's beneficial to add e2e tests for new functionality AND ensure existing functionality is not breaking using e2e tests. To do this, following steps are recommended:

  1. Deploy your new version of operator in a test cluster
  2. Get kubeadmin credentials from your cluster using:
ocm get /api/clusters_mgmt/v1/clusters/(cluster-id)/credentials | jq -r .kubeconfig > /path/to/kubeconfig
  1. Run test suite using:
KUBECONFIG=/path/to/kubeconfig make test-e2e

Or to disable JUnit reports:

DISABLE_JUNIT_REPORT=true KUBECONFIG=/path/to/kubeconfig make test-e2e