Firstly, the whole rule needs to be optional. (E.g., Corvus.SpecFlow.Extensions has no need of this.)
Additionally, there may be cases where not all the measures are applicable. For example, multi-tenancy may be a relevant concern evern where scripting and/or templating are not.
Two options here:
Split this into two rules
Make some measures optional
Moreover, we're not certain the split of measures is correct. E.g. we have "Scripted & Documented", but there may be scenarios where you want deployment concerns documented but there's nothing specific to the component that can be scripted.
idg10
commented
4 years ago
Firstly, the whole rule needs to be optional. (E.g.,
Corvus.SpecFlow.Extensionshas no need of this.)Additionally, there may be cases where not all the measures are applicable. For example, multi-tenancy may be a relevant concern evern where scripting and/or templating are not.
Two options here:
Moreover, we're not certain the split of measures is correct. E.g. we have "Scripted & Documented", but there may be scenarios where you want deployment concerns documented but there's nothing specific to the component that can be scripted.