История

Hongchao Deng f2affa2068 create spec/ pkg and move all specs into it		2016-10-05 15:19:44 -07:00
..
framework	more info at the end of each e2e test	2016-10-04 22:30:01 -07:00
README.md	e2e: support unique namespace each test (#135 )	2016-09-23 16:09:00 -07:00
e2e_test.go	create spec/ pkg and move all specs into it	2016-10-05 15:19:44 -07:00
main_test.go	use persistent storage in backup pod	2016-09-29 20:35:53 -07:00
seed_migration_test.go	create spec/ pkg and move all specs into it	2016-10-05 15:19:44 -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 controller 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" --controller-image gcr.io/coreos-k8s-scale-testing/kube-etcd-controller:latest