-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Upgrade/Downgrade
-
None
-
Fully Compatible
-
v4.9
-
Execution Team 2020-11-30, STM 2021-01-11, STM 2021-01-25, STM 2021-02-08, STM 2021-03-08, STM 2021-03-22, STM 2021-04-05
-
0
-
2
The feature flag-guarding policy states that feature flags should be enabled in the ~ Shared Library Enterprise RHEL 6.2 (disabled feature flags) variant and that tests for flag-guarded features should be tagged with the feature flag name. However, we don't have a mechanism for only running tests for flag-guarded features in the disabled feature flags variant. Current options include excluding those tags from all other variants (which requires too much copy-paste) or creating separate suites that only run in the disabled feature flags variant (which doesn't play well with passthroughs). Additionally, both of these solutions require significant changes to evergreen.yml when the feature flag is enabled.
We should provide an easy and standard way for making sure that tests for flag-guarded features only run in variants in which they are enabled.
- is related to
-
SERVER-56383 Feature flag tag is not preventing a test to run on some non required variants
- Closed
-
SERVER-51112 Make helper for targeted upgrade/downgrade tests
- Closed
-
SERVER-51877 Check that all API Version 1 commands have an associated IDL file specifying inputs/outputs
- Closed
- split to
-
SERVER-53367 Mini-Design to enable feature flag testing with Resmoke
- Closed