Agreed, I really hope this isn't the result of design by committee where each team adds a long list of tests because no one wants to be the one that didn't test

Agreed, I really hope this isn't the result of design by committee where each team adds a long list of tests because no one wants to be the one that didn't test something and lost the vehicle. In software teams, I've seen this issue of too many tests really cripple teams and result in frequent false-positives and products that never make it out the door. Hopefully that's not the case here.