kubernetes/test/e2e/node
Kenichi Omichi c8e0c94a8a Move PrintPerfData to the test
PrintPerfData is called at e2e node tests and it depends on e2elog
and e2emetrics. This moves the function to the place which calls
the function for removing unnecessary dependencies from e2e node
subpackage.
2019-08-23 19:33:24 +00:00
..
apparmor.go remove dot imports in e2e/node 2019-05-12 07:32:26 +08:00
BUILD Move PrintPerfData to the test 2019-08-23 19:33:24 +00:00
crictl.go refactor: replace framework.Failf with e2elog.Failf 2019-06-19 17:52:35 +08:00
events.go e2e: use framework.ExpectEqual() for test/e2e/node 2019-07-04 20:21:04 +08:00
framework.go fix golint error in e2e/node 2019-05-12 07:35:13 +08:00
kubelet.go Use framework functions under test/e2e/node/ 2019-08-21 02:01:49 +00:00
kubelet_perf.go Move PrintPerfData to the test 2019-08-23 19:33:24 +00:00
mount_propagation.go Use framework functions under test/e2e/node/ 2019-08-21 02:01:49 +00:00
node_problem_detector.go Use framework functions under test/e2e/node/ 2019-08-21 02:01:49 +00:00
OWNERS Updated OWNERS files to include link to docs 2019-02-04 22:33:12 +01:00
pod_gc.go refactor: replace framework.Failf with e2elog.Failf 2019-06-19 17:52:35 +08:00
pods.go Use framework functions under test/e2e/node/ 2019-08-21 02:01:49 +00:00
pre_stop.go Move ProxyRequest to kubelet e2e fw 2019-08-13 23:25:47 +00:00
README.md Update deprecated links 2019-02-15 09:13:07 -05:00
security_context.go Use framework functions under test/e2e/node/ 2019-08-21 02:01:49 +00:00
ssh.go refactor: replace framework.Failf with e2elog.Failf 2019-06-19 17:52:35 +08:00
ttlafterfinished.go Use framework functions under test/e2e/node/ 2019-08-21 02:01:49 +00:00

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.