История

Hongchao Deng b0c5002552 tls_test: include client TLS		2017-05-17 13:36:19 -07:00
..
e2eutil	tls_test: include client TLS	2017-05-17 13:36:19 -07:00
framework	*: per cluster s3 policy	2017-05-11 16:11:44 -07:00
upgradetest	upgrade_test: re-enable per cluster S3 tests	2017-05-17 11:08:35 -07:00
README.md	doc: e2e readme update	2016-10-31 14:55:38 -07:00
basic_test.go	e2e: separate cluster and backup deletion checking	2017-05-08 10:26:22 -07:00
cluster_status_test.go	e2e: separate cluster and backup deletion checking	2017-05-08 10:26:22 -07:00
main_test.go	*: rename kube-etcd-controller -> etcd-operator	2016-10-31 10:39:57 -07:00
recovery_test.go	*: per cluster s3 policy	2017-05-11 16:11:44 -07:00
resize_test.go	e2e: separate cluster and backup deletion checking	2017-05-08 10:26:22 -07:00
restore_test.go	*: per cluster s3 policy	2017-05-11 16:11:44 -07:00
self_hosted_test.go	e2e: separate cluster and backup deletion checking	2017-05-08 10:26:22 -07:00
tls_test.go	tls_test: include client TLS	2017-05-17 13:36:19 -07:00
util.go	upgradetest: Add test to restore from backup of old cluster	2017-05-09 14:07:11 -07:00

README.md

E2E Testing

End-to-end (e2e) testing is automated testing for real user scenarios.

Build and run test

Prerequisites:

a running k8s cluster and kube config. We will need to pass kube config as arguments.
Have kubeconfig file ready.
Have etcd operator image ready.

e2e tests are written as go test. All go test techniques applies, e.g. picking what to run, timeout length. Let's say I want to run all tests in "test/e2e/":

$ go test -v ./test/e2e/ --kubeconfig "$HOME/.kube/config" --operator-image=gcr.io/coreos-k8s-scale-testing/etcd-operator