История

Hongchao Deng 318411cf8f minor refactor		2016-10-20 14:54:25 -07:00
..
framework	e2e: increase timeout in setup controller	2016-10-14 11:51:18 -07:00
README.md	e2e: support unique namespace each test (#135 )	2016-09-23 16:09:00 -07:00
e2e_test.go	minor refactor	2016-10-20 14:54:25 -07:00
main_test.go	*: add License header	2016-10-13 16:19:41 -07:00
seed_migration_test.go	e2e: stop etcd after seed test finished	2016-10-17 13:22:06 -07:00
upgrade_test.go	*: add License header	2016-10-13 16:19:41 -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