You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2007/02/13 23:12:05 UTC
[jira] Reopened: (DERBY-2324) convert StmtCloseFunTest to JUnit
[ https://issues.apache.org/jira/browse/DERBY-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reopened DERBY-2324:
---------------------------------------
I don't think it's appropriate to close this issue referring to the jdbc4 test.
Looking at suites/AllPackages.java it appears this test currently only runs with jvms that support jdbc4 (i.e. jdk1.6 (and up, I assume)):
// Suites that are compiled using Java SE 6 target need to
// be added this way, otherwise creating the suite
// will throw an invalid class version error
if (JDBC.vmSupportsJDBC4())
{
suite.addTest(
addSuiteByReflection(
"org.apache.derbyTesting.functionTests.tests.jdbc4._Suite"));
}
Maybe ClosedObjectTest can be run with jdk14/jdk15...But just closing this is not ok, I think.
However, for priority/urgency of this JIRA task: the StmtCloseFunTest now runs under the JDBCHarnessAdapter...
> convert StmtCloseFunTest to JUnit
> ---------------------------------
>
> Key: DERBY-2324
> URL: https://issues.apache.org/jira/browse/DERBY-2324
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Kathey Marsden
> Assigned To: Kathey Marsden
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> Convert StmtCloseFunTest to JUnit to eliminate multiple masters
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.