Hi Julian,
If you pay attention to our CIs (yml files in root of repo) you will see that we
already did some steps to prevent regressions.
There are two types of completely automated testing:
1) tests for Exceptions
2) tests for actual change in violations.
> 1) test for Exceptions
there are property files that describe list of project that do testing.
> 2) tests for actual change in violations
we use certain project that already enforced checkstyle on their codebase , and do each PR validation on them. Look at "NoErrorTest -XXX"
For now it is only 3 project.
=================
if addition to automated testing we ask each contributor to provide as diff-report of violation of Check he update (partly automated process). That is not automated completely .... but one day we will make it.
========================
There are still a lot rooms for improvements in this area, but this is what we have now, if smb want to help us in automatons - be are welcome (I will show places to improve).
thanks,
Roman Ivanov