Feature flagging and testing

212

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.

Avatar
Edith Harbaugh is CEO & Co-Founder of LaunchDarkly, the leading feature management platform. LaunchDarkly serves over a thousand global customers like IBM, Atlassian, and Intuit. She has more than 15 years of experience in engineering, product, and marketing with both consumer and enterprise startups, including TripIt and Concur. She is co-host of "To Be Continuous," a podcast on software trends. She holds two patents in deployment. Edith earned a B.S. in Engineering from Harvey Mudd College.