Categorygithub.com/openshift/cluster-node-tuning-operatorteste2eperformanceprofilefunctestsutilslabel
# Constants
ExperimentalAnnotations ExperimentalAnnotation should be added in tests that test Kubelet changes using experimental annotation.
HyperShift means that tests relevant only for HyperShift platform.
Latency should be added in tests that are meant to test latency sensitivity.
MemoryManager should be added in tests that are meant to test memory manager tests.
MixedCPUs should be added in tests that are validating/verifying mixed-cpus feature functionality.
MustGather should be added in tests that are validating/verifying must-gather tool functionality.
OfflineCPUs should be added in tests that are meant to test offline cpus tests.
OpenShift means that tests are relevant only for OpenShift platform.
OVSPinning should be added in tests that test Dynamic OVS Pinning.
PerformanceProfileCreator should be added in tests that are validating/verifying performance-profile-creator tool functionally.
ReleaseCritical is for tests that are critical for a successful release of the component that is being tested.
RPSMask should be added in tests that are meant to test RPS Masks.
Slow means test that usually requires reboot or takes a long time to finish.
SpecializedHardware is for tests that need special Hardware like SR-IOV devices, specific NICs, etc.
Tier0 are automated unit tests Minimal time needed to execute (minutes to 1 hour) Process criteria: 100% automated, must-pass 100% Development maintains tests, and reviews result.
Tier1 are component level functional tests Minimal time needed to execute (minutes to hours) Process criteria: Executed after tier 0 passing 100% automated and must pass 100% QE / Development maintains tests and reviews results.
Tier2 are integration level functional tests May include basic non-functional tests (security, performance regression, install, compose validation) Runs during nightly time frame Process criteria: Executed after components pass tier 1 testing 100% automated and must pass 100% QE maintains tests and reviews result.
Tier3 are system, scenario and non-functional tests (which includes Fault Tolerance / Recovery / Fail over) Test that don't fit in tier 2 due to time, complexity, and other factors Process criteria: Executed after components pass tier 2 testing System or scenario testing doesn't block Non-functional tests.They can be executed in parallel.
TunedDeferred should be added in tests that test tuned deferred updates annotation.
WorkloadHints should be added in tests that are validating/verifying workload-hints behavior.
# Type aliases
Feature is a label indicates the feature that being tested.
Kind is a label indicates specific criteria that classify the test.
Platform is a label that used to specify the type of platform on which tests are supposed to run.
Tier is a label to classify tests under specific grade/level that should roughly describe the execution complexity, maintainer identity and processing criteria.