When adding a new feature to a chart, it's common practice to protect it beyond a feature flag, like tls.enabled with a default value of false.

This means, though, that simply running helm template in the directory won't catch errors in the chart modifications.

To overcome this, my proposal would be to allow to test with feature flags enabled by:

• Adding a fixtures directory in the chart root
• Add a file for each feature flags, with the list of values to define

CI will then run helm template both on a plain chart and with helm template -f fixtures/$filename for each file in that directory, thus assuring all scenarios we prepared are tested.