[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12370910 ]
David Van Couvering commented on DERBY-1097: -------------------------------------------- There is a jdbc4 suite. You can add any JUnit test to a suite using the .junit extension (e.g. StatementTest.junit). Does that answer your question, Rick? I agree with Rick I don't understand your discussion of the test finding another bug. Did you open a JIRA for the bug? Do you want us to commit it with the known failure and a master file that includes the failure? I would rather see the test code commented out, with a note indicating it's waiting on a fix for JIRA id XXXXX. You know my opinions on patches that are not in svn diff format :) > Add tests for Statement.isClosed() > ---------------------------------- > > Key: DERBY-1097 > URL: http://issues.apache.org/jira/browse/DERBY-1097 > Project: Derby > Type: Sub-task > Components: Test > Versions: 10.2.0.0 > Environment: JDBC4 / JDK 1.6 > Reporter: Kristian Waagan > Assignee: Kristian Waagan > Attachments: StatementTest.java, StatementTest.java-v1, > StatementTestSetup.java, StatementTestSetup.java-v1 > > Add tests for Statement.isClosed() (implemented as part of DERBY-953). > The tests are already written, but because of some "confusion" and diverging > paths regarding how to get connections when running JUnit tests, they are > held back. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
