kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

e2e-tests.md: explain usage of Feature tag for alpha/beta tests 

While we now have the ability to support tests properly which only depend on
alpha or beta feature gates, we still haven't migrated all jobs. So for now,
developers still need to follow the old practice of tagging such tests with
both [Feature] and [FeatureGate].
This commit is contained in:
Patrick Ohly 2024-06-13 09:07:55 +02:00
parent d5a4ac9984
commit b4797e00cd
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
contributors/devel/sig-testing/e2e-tests.md
View File

@ -603,7 +603,13 @@ refine requirements:
Conceptually, these are non-default requirements as defined above under
`[Feature:.+]`, but for historic reasons and the sake of brevity they don't
have that prefix when embedded in test names. They *do* have that prefix in the
Ginkgo v2 label, so use e.g. `--filter-label=Feature: containsAny Alpha`.
Ginkgo v2 label, so use e.g. `--filter-label=Feature: containsAny Alpha` to
run them. The normal `--filter-label=Feature: isEmpty` excludes them.
Note that at the moment, not all jobs filter out tests with `Alpha` or `Beta`
requirements like that. Therefore all tests with such a requirement also
have to be annotated with a `[Feature]` tag. This restriction will be lifted
once migration of jobs to `--filter-label` is completed.
Every test should be owned by a [SIG](/sig-list.md),
and have a corresponding `[sig-<name>]` label.