Hello Allen, Thank you for the detailed reply! I understand and agree with the advantages of splitting the tests. In fact we have experienced some of the disadvantages in our existing approach e.g. checkstyle is run after tests and if tests fail then checkstyle issues are suppressed and it results in more patches. We will follow the zen of Yetus and split checks, but for a quick on boarding and out of curiosity I wanted to know if it is possible to do something like that. This helps a lot.
However, because of some project specific reasons community wants to run all tests to be sure of the patch. This results to another oddity that we don't want to run tests before the patch is applied. I am planning to avoid running tests when there are no java changes and this should help in many scenarios. I will create a profile accordingly. Regards Ajay Yadava
