kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

reorganize doc for easier discovery

This commit is contained in:
Tony Li 2017-02-16 17:33:47 -08:00
parent 5b1da0a8bd
commit 91ca3b62eb
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
contributors/devel/e2e-tests.md
View File

@ -65,7 +65,7 @@ looking to execute or add tests using a local development environment.
Before writing new tests or making substantive changes to existing tests, you Before writing new tests or making substantive changes to existing tests, you
should also read [Writing Good e2e Tests](writing-good-e2e-tests.md) should also read [Writing Good e2e Tests](writing-good-e2e-tests.md)
## Building and Running the Tests ## Building Kubernetes and Running the Tests
There are a variety of ways to run e2e tests, but we aim to decrease the number There are a variety of ways to run e2e tests, but we aim to decrease the number
of ways to run e2e tests to a canonical way: `hack/e2e.go`. of ways to run e2e tests to a canonical way: `hack/e2e.go`.
@ -136,6 +136,14 @@ with this command:
go run hack/e2e.go -- -v --down go run hack/e2e.go -- -v --down
``` ```
## Building the Tests
* You can quickly recompile the e2e testing framework via `go install ./test/e2e`.
This will not do anything besides allow you to verify that the go code compiles.
* If you want to run your e2e testing framework without re-provisioning the e2e setup,
you can do so via `make WHAT=test/e2e/e2e.test` and then re-running the ginkgo tests.
## Advanced testing ## Advanced testing
### Installing/updating kubetest ### Installing/updating kubetest
@ -321,12 +329,6 @@ $ go run hack/e2e.go -- -v --down
Keep in mind that some tests may require multiple underlying clusters and/or minimum compute resource availability. Keep in mind that some tests may require multiple underlying clusters and/or minimum compute resource availability.
* You can quickly recompile the e2e testing framework via `go install ./test/e2e`. This will not do anything besides
allow you to verify that the go code compiles.
* If you want to run your e2e testing framework without re-provisioning the e2e setup, you can do so via
`make WHAT=test/e2e/e2e.test` and then re-running the ginkgo tests.
* If you're hacking around with the federation control plane deployment itself, * If you're hacking around with the federation control plane deployment itself,
you can quickly re-deploy the federation control plane Kubernetes manifests without tearing any resources down. you can quickly re-deploy the federation control plane Kubernetes manifests without tearing any resources down.
To re-deploy the federation control plane after running `--up` for the first time: To re-deploy the federation control plane after running `--up` for the first time: