From 91f49abbf8d5b08cd8a2ad4fac4aefe2f2fe73aa Mon Sep 17 00:00:00 2001 From: Michelle Au Date: Thu, 26 Jan 2017 16:02:03 -0800 Subject: Update e2e doc to add [Volume] label. --- contributors/devel/e2e-tests.md | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'contributors') diff --git a/contributors/devel/e2e-tests.md b/contributors/devel/e2e-tests.md index 9d83f7f9..01499ccf 100644 --- a/contributors/devel/e2e-tests.md +++ b/contributors/devel/e2e-tests.md @@ -480,6 +480,15 @@ 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. + ### Viper configuration and hierarchichal test parameters. The future of e2e test configuration idioms will be increasingly defined using viper, and decreasingly via flags. -- cgit v1.2.3