[ http://issues.apache.org/jira/browse/DERBY-919?page=comments#action_12370620 ]
Kristian Waagan commented on DERBY-919: --------------------------------------- Do we still need to have clients for both DB2 JCC and the "old net" framework? Based on contents of various classes, there seem to be some confusion (ie. that DB2JCC has JDBC prefix "jdbc:derby:net", others use "jdbc:db2:"). Am I correct when saying we only need the "jdbc:derby:net" framework in the JDBCClient class, and that this client should be named either "DERBYNET" or "JCC"? (but not "DB2JCC", as this imply we are connecting to DB2, not Derby) Is the EmbeddedSimpleDataSource the only mean to create a connection in JSR 169? > improve pattern for setting up junit tests > ------------------------------------------ > > Key: DERBY-919 > URL: http://issues.apache.org/jira/browse/DERBY-919 > Project: Derby > Type: Sub-task > Components: Test > Environment: All > Reporter: Andreas Korneliussen > Attachments: BasicDerbyJUnitTest.html, BasicDerbyJUnitTest.java, > BasicDerbyJUnitTestTest.java, JDBCClient.java, TestConfiguration.java > > The current junit tests cannot be run directly from the java.ui.textrunner by > i.e using: > java junit.textui.TestRunner > org.apache.derbyTesting.functionTests.tests.junitTests.lang.BooleanTest > .E > Time: 0.008 > There was 1 error: > 1) > testBoolean(org.apache.derbyTesting.functionTests.tests.junitTests.lang.BooleanTest)java.lang.NullPointerException > at > org.apache.derbyTesting.functionTests.util.DerbyJUnitTest.faultInDriver(DerbyJUnitTest.java:317) > at > org.apache.derbyTesting.functionTests.util.DerbyJUnitTest.getConnection(DerbyJUnitTest.java:345) > at > org.apache.derbyTesting.functionTests.util.DerbyJUnitTest.getConnection(DerbyJUnitTest.java:335) > at > org.apache.derbyTesting.functionTests.tests.junitTests.lang.BooleanTest.testBoolean(BooleanTest.java:136) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > FAILURES!!! > Tests run: 1, Failures: 0, Errors: 1 > The reason is that the tests needs to have some fixture being set up before > the test can run, and that this is currently supported by calling a bunch of > static methods in the correct order to initialize some static members of > DerbyJUnitTest. > The proposed alternative is that the added fixture is set up in the suite() > method, which is used by JUnit to get the Test object to be run. -- 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
