2016-09-12 21:59:44 +03:00
|
|
|
# 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.
|
2016-09-24 02:09:00 +03:00
|
|
|
- Have kubeconfig file ready.
|
2016-10-31 23:25:09 +03:00
|
|
|
- Have etcd operator image ready.
|
2016-09-12 21:59:44 +03:00
|
|
|
|
|
|
|
|
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/":
|
|
|
|
|
```
|
2016-10-31 20:02:02 +03:00
|
|
|
$ go test -v ./test/e2e/ --kubeconfig "$HOME/.kube/config" --controller-image gcr.io/coreos-k8s-scale-testing/etcd-operator:latest
|
2016-09-16 01:31:45 +03:00
|
|
|
```
|
