Recommended approach for automated testing of both code paths in ASP.NET Core? about featuremanagement-dotnet HOT 2 CLOSED

If you are just testing the application's ability to react on feature manager evaluations then I would say that stubbing the feature manager is a proper way to accomplish this. You could create a test implementation of IFeatureManager which contains the desired state of all features as a dictionary.

I wouldn't say that there is a one solution fits all approach. Some tests may require a more dynamic approach and in that case you could directly interact with a TestFilter as shown in this code snippet:

from featuremanagement-dotnet.

Thanks, Jimmy.

Just to clarify, the reason behind my question was based on this excerpt from Pete Hodgson's article on Martin Fowler's blog:

We can create a new toggle router based on some default configuration - perhaps read in from a config file - but we can also dynamically toggle a feature on or off. This allows automated tests to verify both sides of a toggled feature:

Also,

You could create a test implementation of IFeatureManager which contains the desired state of all features as a dictionary.

Good point. I realize the stubbing approach in #19 (comment) would degrade in maintainability as the # of features grows. I hadn't fully thought that threw so I'll definitely take this into consideration.

from featuremanagement-dotnet.