diff options
| author | Jun Xiang Tee <juntee@google.com> | 2017-07-14 13:39:56 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-07-14 13:39:56 -0700 |
| commit | 3016b81ef8d0fbca1068791949371d17b14e42d9 (patch) | |
| tree | e6ac7dfcf46eba150f484d105395a2a7695436fc | |
| parent | 7d705d6802e54c37f739d1b05deac0995ce54ea4 (diff) | |
Add more information for e2e.test
| -rw-r--r-- | contributors/devel/e2e-tests.md | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/contributors/devel/e2e-tests.md b/contributors/devel/e2e-tests.md index eefe583b..15d46a50 100644 --- a/contributors/devel/e2e-tests.md +++ b/contributors/devel/e2e-tests.md @@ -145,7 +145,13 @@ go run hack/e2e.go -- -v --down 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. + you can do so via `make WHAT=test/e2e/e2e.test` + +* You can then create a symlink pointing `e2e.test` to `_output/local/bin/linux/amd64/e2e.test`, + and re-run the ginkgo tests by providing relevant flags. For example: +```sh +e2e.test --host="127.0.0.1:8080" --provider="local" --repo-root="path/to/main/repo" --kubeconfig="path/to/.kube/config" --ginkgo.focus="regex" +``` ## Advanced testing |