Update documentation for running e2e tests locally

The docs for running e2e tests locally needs to be updated. check_node_count option has been removed and developers usually need to perform additional steps do get it going.

Update documentation for running e2e tests locally
4c0f3b84 · Hemant Kumar · 189bb742 · 4c0f3b84
Commit 4c0f3b84 authored Oct 06, 2016 by Hemant Kumar
Hide whitespace changes
Inline Side-by-side

Showing with 6 additions and 1 deletion

e2e-tests.md docs/devel/e2e-tests.md +6 -1

No files found.
--- a/docs/devel/e2e-tests.md
+++ b/docs/devel/e2e-tests.md
@@ -383,6 +383,9 @@ sudo PATH=$PATH hack/local-up-cluster.sh
 This will start a single-node Kubernetes cluster than runs pods using the local
 docker daemon. Press Control-C to stop the cluster.

+You can generate a valid kubeconfig file by following instructions printed at the
+end of aforementioned script.
+
 #### Testing against local clusters

 In order to run an E2E test against a locally running cluster, point the tests
@@ -390,7 +393,9 @@ at a custom host directly:

 ```sh
 export KUBECONFIG=/path/to/kubeconfig
-go run hack/e2e.go -v --test --check_node_count=false
+export KUBE_MASTER_IP="http://127.0.0.1:<PORT>"
+export KUBE_MASTER=local
+go run hack/e2e.go -v --test
 ```

 To control the tests that are run: