[DERBY-6073] Test ordering instability in StatementPoolingTest

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.9.1.0, 10.10.1.1
• Fix Version/s: 10.10.1.1
• Component/s: Test
• Environment: Java 7, Java 8
• Urgency: Normal
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 15/Feb/13 16:11
• Updated: 12/Mar/13 08:25
• Resolved: 12/Mar/13 08:25

Description

StatementPoolingTest.testPoolingEnabledByCheckingImplementationDetails() assumes that the client-side statement cache will have been primed by a previous test case, testCacheOverflow(). On Java 7 and Java 8 the test order is not deterministic. If testPoolingEnabledByCheckingImplementationDetails() is the first test case to run, then it fails with this error:

org.apache.derbyTesting.functionTests.tests.jdbcapi.StatementPoolingTest.assertClassName(StatementPoolingTest.java:147)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.StatementPoolingTest.testPoolingEnabledByCheckingImplementationDetails(StatementPoolingTest.java:89)

I will attach a patch which forces testPoolingEnabledByCheckingImplementationDetails() to be first in the test order. With this patch, StatementPoolingTest fails for me on Java 7 when run on the 10.9 branch as well as on trunk.

Issue Links

• relates to: DERBY-6000 Implement support for JDBC 4.2