diff options
| author | Tony Li <tonyli.lives@gmail.com> | 2017-02-16 17:33:47 -0800 |
|---|---|---|
| committer | Tony Li <tonyli.lives@gmail.com> | 2017-02-16 17:33:47 -0800 |
| commit | 91ca3b62ebc9f16a7f54df525f41b767cb78e71b (patch) | |
| tree | de45446f73c48b4c3d2528035e0a858aaac58dac | |
| parent | 5b1da0a8bd030964207a9277870a4764209352a2 (diff) | |
reorganize doc for easier discovery
| -rw-r--r-- | contributors/devel/e2e-tests.md | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/contributors/devel/e2e-tests.md b/contributors/devel/e2e-tests.md index b5b05d78..2bdf9069 100644 --- a/contributors/devel/e2e-tests.md +++ b/contributors/devel/e2e-tests.md @@ -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 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 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 ``` +## 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 ### 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. -* 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, 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: |