Hi, Gunnar Morling I was looking at this one - something like

TestUtil#getConstraintViolationForConstraintType

wouldn't work in all cases. For example I found one testcase where there are two violations for Max - just on a different properties. So for such cases maybe something like

TestUtil#getConstraintViolationForConstraintTypeAndPropertyPath

would work...
Would such changes be useful? If so - I can work on them.