README
¶
Automated Test Harness
This test harness is used to verify that the kube examples are working as intended as
part of an integration test suite. This harness will deploy the examples, query the Kubeneretes
API using client-go and run various tests against the deployments.
The test harness creates namespaces for each test to avoid collision with object names.
This harness can be run both in and out of a Kubernetes cluster.
Prerequisites
- An account with sufficient privileges is required (cluster-admin).
- It's recommended that all images used in the testing should be pulled prior to running the harness. Pulling images over the network may be slow and cause timeouts with the harness.
- The
kubeconfigshould be found in$HOME/.kube/config - Mercurial Version Control installed (installed in
install-deps.shif you're using CentOS7) GOMAXPROCSenv should be set to the amount of cores the test harness should use (parallization option)
Configuration
The following environment variables can be used to configure the test harness:
| Name | Default | Description |
|---|---|---|
CCP_HARNESS_CLEANUP |
true | Configures the harness to run cleanup scripts after tests are complete. |
CCP_HARNESS_DEBUG |
true | Configures the harness to log the output of the scripts being executed. |
CCP_HARNESS_IN_CLUSTER |
false | Configures the harness to run in/out of a Kubernetes cluster. |
To export these environment variables, run the following commands:
export CCP_HARNESS_CLEANUP=true
export CCP_HARNESS_DEBUG=true
export CCP_HARNESS_IN_CLUSTER=false
Running
Note: It's recommended to disable the go test timeout (it defaults to 10 minutes which
is not enough time to run all tests):
Go 1.9
go test -timeout 100m (100 minutes)
Go 1.10+
go test -timeout 0
All Tests
Run all tests, no timeout, max of 2 tests in parallel:
cd $CCPROOT/tools/test-harness
go test -v -timeout 0 -parallel 2
Running Specific Tests
Using regex, run the TestPrimary test ($ is regex for the string ends,
meaning it won't match on say TestPrimaryReplica)
cd $CCPROOT/tools/test-harness
go test -v -run TestPrimary$
Manual Cleanup
If for some reason the test-harness crashes, it's possible the test-harness namespaces have not been cleaned up correctly. To manually delete the test harness namespaces, run the following script:
${CCPROOT?}/tools/test-harness/test-harness-manual-cleanup.sh
Directories