diff options
| author | Isaac Hollander McCreery <ihmccreery@google.com> | 2016-01-29 16:23:59 -0800 |
|---|---|---|
| committer | Isaac Hollander McCreery <ihmccreery@google.com> | 2016-01-29 16:23:59 -0800 |
| commit | d4d8eb42e09e50e41d71a698d21b7dc2ef348b0b (patch) | |
| tree | 98a4b8e80d5aede4471567b5241b8e9b70e5bba0 /e2e-tests.md | |
| parent | 8326bbc4f6ba090207364a41bfa2b1f0feca466f (diff) | |
Add docs about the PR builder
Diffstat (limited to 'e2e-tests.md')
| -rw-r--r-- | e2e-tests.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/e2e-tests.md b/e2e-tests.md index 63ebd16e..12915543 100644 --- a/e2e-tests.md +++ b/e2e-tests.md @@ -141,6 +141,10 @@ We also run non-default tests if the tests exercise general-availability ("GA") Many `[Feature:.+]` tests we don't run in CI. These tests are for features that are experimental (often in the `experimental` API), and aren't enabled by default. +### The PR-builder + +We also run a battery of tests against every PR before we merge it. These tests are equivalent to `kubernetes-gce`: it runs all non-`[Slow]`, non-`[Serial]`, non-`[Disruptive]`, non-`[Flaky]`, non-`[Feature:.+]` tests in parallel. These tests are considered "smoke tests" to give a decent signal that the PR doesn't break most functionality. Results for you PR can be found at [pr-test.k8s.io](pr-test.k8s.io), e.g. [pr-test.k8s.io/20354](pr-test.k8s.io/20354) for #20354. + ### Adding a test to CI As mentioned above, prior to adding a new test, it is a good idea to perform a `-ginkgo.dryRun=true` on the system, in order to see if a behavior is already being tested, or to determine if it may be possible to augment an existing set of tests for a specific use case. |