How to change the default behaviour of FeatureContext for Cucumber Tests

[EAlf91]

Currently I'm facing the issue that I want to disable my features when running cucumber tests to not interfere with the old behaviour of the app.

I configured the TestFeatureManager for this and added this for my feature files and the test steps

@Autowire 
FeatureManager featureManager

@Before("@FeaturesDisabled")
public void disableFeatures(Scenario scenario) {

    featureManager.disable(MyFeatures.HELLO_WORLD);
}

Unfortunately, while the featuremanager get's properly injected in my tests, the application code uses the enum method, which always returns some FallBacktestFeatureManager:

FeatureContext.getFeatureManager() //does not return the configured Featuremanager

Is it possible to customize the FeatureContext?

[brunojanvier77]

We also need the same thing. +1
Possibility to customize so that the default test behavior is that the flags are disabled to match production conditions.