-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
DevProd Correctness
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
runNoFeatureFlagTests should be renamed to excludeUnreleasedFeatureFlagTests
runAllFeatureFlagTests should be renamed to activateUnreleasedFeatureFlags
The old arguments should be kept for backwards compatibility and deprecated with warnings about using the new options instead.
The --help for these options should also be updated, here are some descriptions that might help.
Using -runNoFeatureFlagTests will simply add all “featureFlags” (entries in all_feature_flags.txt ) to the -excludeWithAnyTags argument. If you use this argument & your “featureFlag” does not have a default version, it’s corresponding tests are guaranteed to be ignored during testing. This is an override used for multiversion testing.
Using --runAllFeatureFlagTests will activate all “featureFlags” from the all_feature_flags.txt file but does not actually “runAllFeatureFlagTests” as indicated by the name and resmoke arg description. This does not affect includes/excludes or what tests run, it simply “turns on” all feature flags.
There is another ticket about changing the name of all_feature_flags.txt to unreleased_feature_flags.txt in case that one gets done first and this description becomes outdated.