> So your release which is "safer" behind a flag is actually untested until it's launched.

It's only untested if your intention is to not test it.

There is nothing preventing you from testing a feature flag in e2e tests. In fact, testing is perhaps the primary reason why user overrides are supported by feature flag systems.

how? if you have 100 feature flags in your system each with 3 potential states, which states do you run in your e2es?