From fec70556e9109c1eb3930745e07c0853d193eab3 Mon Sep 17 00:00:00 2001 From: Michelle Au Date: Wed, 2 Aug 2017 19:19:07 -0700 Subject: [PATCH] Update e2e doc to add sig labels --- contributors/devel/e2e-tests.md | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/contributors/devel/e2e-tests.md b/contributors/devel/e2e-tests.md index eefe583b6..2bfc6f825 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-]` label. ### Viper configuration and hierarchichal test parameters.