Feature flagging and testing

LaunchDarkly
By Edith Harbaugh   •   August 22, 2016
LaunchDarkly

Sam Stokes, Rapportive co-founder, has this tip on testing and feature flagging:

"I've found that explicitly testing both sides of the flag can help with managing the increased complexity a flag introduces.  It helps you catch changes down the line that would have broken the old, forgotten code path that 10% of customers are still on.  It provides reminders to clean up the old code and delete the flag (via occasionally breaking the tests).  And it provides some pushback against having too many interacting flags (if you had to write 8 tests for one function because it depended on three separate feature flags, maybe it's time to refactor that function, or retire some flags)."

Sam Stokes regularly blogs here.

You May Like
  •   BEST PRACTICESTesting in Production to Stay Safe and Sensible
  •   BEST PRACTICESWhat Is Continuous Testing? A Straightforward Introduction
MAY 14, 2021   •   BEST PRACTICESCloud Deployment Models: Explaining and Comparing the 5 Main Models
MAY 11, 2021   •   BEST PRACTICESWhat Is Deployment Automation, and Why Should You Care?
MAY 6, 2021   •   BEST PRACTICESRelease Testing Explained
MAY 4, 2021   •   BEST PRACTICESOrchestration vs. Automation in the Cloud: How to Use Both