Files

Justin Santa Barbara 153f91693b e2e: change test strings to avoid error highlighting

The words "error" and "fail" are magic in test output, and are
highlighted in the build logs.  Change some test strings to avoid
hitting the highlighting in normal operation.

2018-10-03 09:37:26 -07:00

apparmor.go

enable to specific unconfined AppArmor profile

2017-09-28 10:06:36 +08:00

BUILD

GCE: add a crictl test

2018-08-08 10:25:17 -07:00

crictl.go

GCE: add a crictl test

2018-08-08 10:25:17 -07:00

events.go

Merge pull request #66209 from tianshapjq/should-not-fmtprintf

2018-08-17 02:27:10 -07:00

framework.go

Rename e2e sig framework files

2017-08-02 09:33:19 +08:00

kubelet_perf.go

Remove e2e-image-puller

2018-09-03 20:43:54 -04:00

kubelet.go

e2e test harness - use busybox from dockerhub

2018-08-07 11:22:16 -04:00

mount_propagation.go

e2e test harness - use busybox from dockerhub

2018-08-07 11:22:16 -04:00

OWNERS

…

pod_gc.go

e2e test harness - use busybox from dockerhub

2018-08-07 11:22:16 -04:00

pods.go

Update the nginx image from hub.docker.com

2018-08-04 05:19:53 +05:30

pre_stop.go

e2e test harness - use busybox from dockerhub

2018-08-07 11:22:16 -04:00

README.md

Add a README in test/e2e/node with a warning

2018-07-06 16:48:35 -07:00

security_context.go

e2e test harness - use busybox from dockerhub

2018-08-07 11:22:16 -04:00

ssh.go

e2e: change test strings to avoid error highlighting

2018-10-03 09:37:26 -07:00

README.md

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.