mirror of
https://github.com/k3s-io/kubernetes.git
synced 2026-07-18 04:54:54 +00:00
c5e4cab9b1
there are many cases of an e2e feature being the main filtering mechanism for a test. However, this makes it tricky for suite authors to filter tests based on available features. This mechanism is still useful for e.g. making sure a runtime on a suite is of the correct level, but in general we should both label tests with the Feature set they require (whether runtime is correct) as well as the feature gates they test. Signed-off-by: Peter Hunt <pehunt@redhat.com>
WARNING: Do not add tests in this directory
There are two types of end-to-end tests in Kubernetes:
Tests located in ${KUBE_ROOT}/test/e2e/common are shared by both Cluster
and Node E2E test jobs. Tests in ${KUBE_ROOT}/test/e2e_node are exclusively
owned by Node E2E. If you want to add a test, most likely than not, you want
to add the test to one of the two directories mentioned above. If you are
unsure, please check with the OWNER of the directory. This directory currently
contains misplaced and legacy tests; they will be cleaned up in the future.