mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-03-30 14:25:38 -04:00
d4729008ef
ginkgo.DeferCleanup has multiple advantages: - The cleanup operation can get registered if and only if needed. - No need to return a cleanup function that the caller must invoke. - Automatically determines whether a context is needed, which will simplify the introduction of context parameters. - Ginkgo's timeline shows when it executes the cleanup operation. |
||
|---|---|---|
| .. | ||
| apparmor.go | ||
| crictl.go | ||
| events.go | ||
| examples.go | ||
| framework.go | ||
| kubelet.go | ||
| kubelet_perf.go | ||
| mount_propagation.go | ||
| node_problem_detector.go | ||
| OWNERS | ||
| pod_gc.go | ||
| pods.go | ||
| pre_stop.go | ||
| README.md | ||
| runtimeclass.go | ||
| security_context.go | ||
| ssh.go | ||
| taints.go | ||
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.