I view feature flags as having a short life cycle, ideally. Because of that, I make sure to have tests that cover both when a flag is enabled and disabled, but I try to keep flags cleaned out of the code after they've been deployed and released to reduce the permutation scenario that you're describing.
In practice, I find that this kind of feature flag hygiene means that the number of interacting flags is pretty low so there doesn't have to be too many overlapping tests.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Cool, glad you like it!
I view feature flags as having a short life cycle, ideally. Because of that, I make sure to have tests that cover both when a flag is enabled and disabled, but I try to keep flags cleaned out of the code after they've been deployed and released to reduce the permutation scenario that you're describing.
In practice, I find that this kind of feature flag hygiene means that the number of interacting flags is pretty low so there doesn't have to be too many overlapping tests.