-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Replication
The requires_fcv_5x and requires_fcv_60 can simply be removed
The requires_fcv_61 tag should be replaced with the appropriate feature flag tag if the test depends on a specific feature flag
Edit: We currently cannot actually stop using requires_fcv_yy since if we have a feature flag that is enabled, (either through running in an all feature flags variant, or through being enabled by default), and we have a test that tests this feature, the featureFlagXX tag would not prevent it from being run on sharding_multiversion, so we should be tagging it with requires_fcv_yy.
The current guidance for feature flag test tagging is here, but it is slightly complicated, so we should investigate simplifying this. Additionally, we should investigate moving away from using FeatureFlagUtil.isEnabled where possible, since it is wasteful to start up a whole cluster only to see that the feature flag is not enabled and then skip the whole test.
- depends on
-
SERVER-71467 Dont run feature flag specific tests for multiversion testing
-
- Closed
-
- duplicates
-
SERVER-69883 Investigate improving JS test tags for tests dependent on in-development or recently-released feature work
-
- Open
-
- is related to
-
-
- Closed
-
-
-
- Open
-
- related to
-
-
- Closed
-