DevFW-CICD/ingress-nginx-helm
16
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

up update e2e command to main repo format

Browse source
This commit is contained in:
Tony Li 2017-02-16 17:40:10 -08:00
parent 5f8a40d392
commit 7286d528a4
1 changed files with 8 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
docs/dev/releases.md
View file

@ -64,20 +64,24 @@ git commit
## Testing ## 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 ```console
$ cd $GOPATH/src/k8s.io/ingress/controllers/gce $ cd $GOPATH/src/k8s.io/ingress/controllers/gce
$ go test ./... $ go test ./...
``` ```
### e2e tests
If you have access to a Kubernetes cluster, you can also run e2e tests If you have access to a Kubernetes cluster, you can also run e2e tests
```console ```console
$ cd $GOPATH/src/k8s.io/kubernetes $ 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 [TODO](https://github.com/kubernetes/ingress/issues/5): add instructions on running integration tests, or e2e against
local-up/minikube. local-up/minikube.