diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-07-11 09:57:26 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-07-11 09:57:26 -0700 |
| commit | 2bd846d0146eaae9dd9f0d2138c6b2177fbe04fc (patch) | |
| tree | 65f0f07719c86b26c157ece159f3db84c43176e2 | |
| parent | 35b3e3cf65211fb999811a563b6f4c9f92a929c3 (diff) | |
| parent | 2a6c6d12a499f8be01c290b1e04714f392b501c9 (diff) | |
Merge pull request #2362 from krzyzacy/fix-e2e
replace e2e-runner with kubetest
| -rw-r--r-- | contributors/devel/e2e-tests.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/e2e-tests.md b/contributors/devel/e2e-tests.md index 67453ba5..15f2a373 100644 --- a/contributors/devel/e2e-tests.md +++ b/contributors/devel/e2e-tests.md @@ -460,7 +460,7 @@ similarly enough to older versions. The general strategy is to cover the follow same version (e.g. a cluster upgraded to v1.3 passes the same v1.3 tests as a newly-created v1.3 cluster). -[hack/e2e-runner.sh](https://git.k8s.io/test-infra/jenkins/e2e-image/e2e-runner.sh) is +[kubetest](https://git.k8s.io/test-infra/kubetest) is the authoritative source on how to run version-skewed tests, but below is a quick-and-dirty tutorial. |