From 7286d528a4af11e1178c4349d948a173c3efaa18 Mon Sep 17 00:00:00 2001
From: Tony Li <tony.li@nytimes.com>
Date: Thu, 16 Feb 2017 17:40:10 -0800
Subject: [PATCH] up update e2e command to main repo format

---
 docs/dev/releases.md | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/docs/dev/releases.md b/docs/dev/releases.md
index ce613cc23..31c83f928 100644
--- a/docs/dev/releases.md
+++ b/docs/dev/releases.md
@@ -64,20 +64,24 @@ git commit
 
 ## Testing
 
-To run unittets, enter each directory in `controllers/`
+See also [related FAQs](../faq#how-are-the-ingress-controllers-tested).
+
+### Unit tests
+
+To run unit tests, enter each directory in `controllers/`
 ```console
 $ cd $GOPATH/src/k8s.io/ingress/controllers/gce
 $ go test ./...
 ```
 
+### e2e tests
+
 If you have access to a Kubernetes cluster, you can also run e2e tests
 ```console
 $ cd $GOPATH/src/k8s.io/kubernetes
-$ ./hack/ginkgo-e2e.sh --ginkgo.focus=Ingress.* --delete-namespace-on-failure=false
+$ go run hack/e2e.go -- -v --test --test_args="--ginkgo.focus=Ingress.* --delete-namespace-on-failure=false"
 ```
 
-See also [related FAQs](../faq#how-are-the-ingress-controllers-tested).
-
 [TODO](https://github.com/kubernetes/ingress/issues/5): add instructions on running integration tests, or e2e against
 local-up/minikube.