Files
kubernetes/test/cmd
2020-01-10 09:39:54 +08:00
..
2019-10-23 22:47:47 +02:00
2019-06-04 14:42:01 +08:00
2019-11-15 11:50:58 -08:00
2019-10-23 22:47:47 +02:00
2019-10-23 22:47:47 +02:00
2019-11-13 14:20:19 -08:00
2019-11-07 02:26:45 -05:00
2019-06-17 14:04:34 +08:00
2019-02-21 06:15:13 -05:00
2019-09-15 13:55:48 +08:00
2019-10-23 22:47:47 +02:00

Kubernetes Command-Line Integration Test Suite

This document describes how you can use the Kubernetes command-line integration test-suite.

Running Tests

All Tests

To run this entire suite, execute make test-cmd from the top level. This will import each file containing tests functions

Specific Tests

To run a subset of tests (e.g. run_deployment_test and run_impersonation_test), execute make test-cmd WHAT="deployment impersonation". Running specific tests will not try and validate any required resources are available on the server.

Adding Tests

Test functions need to have the format run_*_test so they can executed individually. Once a test has been added, insert a section in legacy-script.sh like

######################
# Replica Sets       #
######################

if kube::test::if_supports_resource "${replicasets}" ; then
    record_command run_rs_tests
fi

Be sure to validate any supported resouces required for the test by using the kube::test::if_supports_resource function.

New File

If the test resides in a new file, source the file in the top of the legacy-script.sh file by adding a new line in

source "${KUBE_ROOT}/test/cmd/apply.sh"
source "${KUBE_ROOT}/test/cmd/apps.sh"
source "${KUBE_ROOT}/test/cmd/authorization.sh"
source "${KUBE_ROOT}/test/cmd/batch.sh"
...

Please keep the order of the source list alphabetical.