Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • You don't have to test each combination of feature toggles. You mostly need to test the combination(s) that you intended to use when the code under test is released. Generally this is just one or two combinations. Commented Oct 25, 2019 at 11:03
  • @bdsl true, if you never toggle a feature, but this would be the same as commenting out code. There would be no purpose to the toggle. Commented Oct 25, 2019 at 13:15
  • Feature toggles look a little loose (ie, easy to forget about and accidentally release the wrong version). Commented Oct 25, 2019 at 19:05
  • @danwoz: only when used in an non-systematic way, or when applied wrong. Commented Oct 27, 2019 at 13:32
  • @Ewan: the same argument you gave against feature toggles could be applied to any (regular) configuration option in an application. And just because an application allows lot of configuration options, it does not become "untestable". Commented Oct 27, 2019 at 13:36