Tag Info

Hot answers tagged

2

The short answer is that you can never be 100% sure. The longer answer is that this is also true for every other part of the product- you test it but can never test it for every possible scenario. The even longer answer is risk management and mitigation- your developers and architects need to asses the risk in solutions A and B (feature flags vs. ...


1

I am a BIG fan of feature toggles. It doesn't take too much work to mitigate the risks, and the benefits are well worth it. So my question is toggling unused feature enough to release untested code? No. Feature toggles are not enough to mitigate the risks posed by releasing completely untested code. However, when you test around that code, feature ...


1

This is usually referred as A/B testing. I have personally tested this. With Feature Enabled - Testing performed for new feature and regression to ensure nothing is broken With Feature Disabled - Regression performed to ensure functionality remains intact. Automation / Required Manual tests will be run in case if this code is going to remain in production ...



Only top voted, non community-wiki answers of a minimum length are eligible