diff --git a/rm-server/unit-test/java/org/alfresco/module/org_alfresco_module_rm/test/util/ExceptionUtils.java b/rm-server/unit-test/java/org/alfresco/module/org_alfresco_module_rm/test/util/ExceptionUtils.java index f82c213df0..8a6d648c4c 100644 --- a/rm-server/unit-test/java/org/alfresco/module/org_alfresco_module_rm/test/util/ExceptionUtils.java +++ b/rm-server/unit-test/java/org/alfresco/module/org_alfresco_module_rm/test/util/ExceptionUtils.java @@ -75,12 +75,13 @@ public class ExceptionUtils } /** - * Utility method to help with expected exceptions in test code. This can be used in place of {@code try/catch} - * blocks within test code and can sometimes make code more readable. + * Utility method to help with expected exceptions (unchecked - see below) in test code. This can be used in place + * of {@code try/catch} blocks within test code and can sometimes make code more readable. * A single expected exception would usually be let escape from the test method and be handled e.g. by JUnit's * {@code @Test(expected="Exception.class")} pattern. * However if you have multiple expected exceptions in a sequence, you need to either add a sequence of - * {@code try/catch} or use this method. + * {@code try/catch} or use this method. Likewise if you need to make assertions about state within the expected + * exception, such as root cause or other internal state, this method will be useful. *
* Examples: *