db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Korneliussen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-919) improve pattern for setting up junit tests
Date Fri, 03 Feb 2006 12:25:03 GMT
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
 Assigned to: Andreas Korneliussen 

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
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)

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:
For more information on JIRA, see:

View raw message