summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorgrodrigues3 <grodrigues3@gmail.com>2017-08-04 14:28:24 -0700
committerGitHub <noreply@github.com>2017-08-04 14:28:24 -0700
commitb56f18ef51ab102e5c8c675f55cf437fa05ccf75 (patch)
tree755c45e146844a53541b1e60bdfcbd9b0a27ce5f
parentd29f514e1516e22bb83d443d4bc621bba2b5cef3 (diff)
parentfec70556e9109c1eb3930745e07c0853d193eab3 (diff)
Merge pull request #875 from msau42/e2e-volume-label
Update e2e doc to add sig labels
-rw-r--r--contributors/devel/e2e-tests.md10
1 files changed, 2 insertions, 8 deletions
diff --git a/contributors/devel/e2e-tests.md b/contributors/devel/e2e-tests.md
index eefe583b..2bfc6f82 100644
--- a/contributors/devel/e2e-tests.md
+++ b/contributors/devel/e2e-tests.md
@@ -581,14 +581,8 @@ breaking changes, it does *not* block the merge-queue, and thus should run in
some separate test suites owned by the feature owner(s)
(see [Continuous Integration](#continuous-integration) below).
-In order to simplify running component-specific test suites, it may also be
-necessary to tag tests with a component label. The component may include
-standard and non-standard tests, so the `[Feature:.+]` label is not sufficient for
-this purpose. These component labels have no impact on the standard e2e test
-suites. The following component labels have been defined:
-
- - `[Volume]`: All tests related to volumes and storage: volume plugins,
-attach/detatch controller, persistent volume controller, etc.
+Every test should be owned by a [SIG](https://github.com/kubernetes/community/blob/master/sig-list.md),
+and have a corresponding `[sig-<name>]` label.
### Viper configuration and hierarchichal test parameters.