From 3370f0125acc739c5b7aeae844cf396eae7dc01d Mon Sep 17 00:00:00 2001 From: Sebastian Bazley Date: Wed, 5 Feb 2014 18:46:27 +0000 Subject: [PATCH] Identify the assertion failure git-svn-id: https://svn.apache.org/repos/asf/commons/proper/logging/trunk@1564876 13f79535-47bb-0310-9956-ffa450edef68 --- .../commons/logging/security/SecurityAllowedTestCase.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/test/java/org/apache/commons/logging/security/SecurityAllowedTestCase.java b/src/test/java/org/apache/commons/logging/security/SecurityAllowedTestCase.java index 3247ef4..b957237 100644 --- a/src/test/java/org/apache/commons/logging/security/SecurityAllowedTestCase.java +++ b/src/test/java/org/apache/commons/logging/security/SecurityAllowedTestCase.java @@ -125,7 +125,7 @@ public class SecurityAllowedTestCase extends TestCase // we better compare that we have no security exception during the call to log // IBM JVM tries to load bundles during the invoke call, which increase the count - assertEquals(untrustedCodeCount, mySecurityManager.getUntrustedCodeCount()); + assertEquals("Untrusted code count", untrustedCodeCount, mySecurityManager.getUntrustedCodeCount()); } catch(Throwable t) { // Restore original security manager so output can be generated; the // PrintWriter constructor tries to read the line.separator