In the future, we might want to add more tests with failure cases. If we have travis or jenkins or something running against an assortment of prior distributions, it could give confidence that new changes don't make other projects now invalid, or better yet that ones that should be invalid are now invalid.
This will likely be more important when there's more diversity than just maven projects, or projects outside zipkin.
I was thinking maybe a unit test that took parameters used in release votes and asserts that they still pass.
In the future, we might want to add more tests with failure cases. If we have travis or jenkins or something running against an assortment of prior distributions, it could give confidence that new changes don't make other projects now invalid, or better yet that ones that should be invalid are now invalid.
This will likely be more important when there's more diversity than just maven projects, or projects outside zipkin.
I was thinking maybe a unit test that took parameters used in release votes and asserts that they still pass.