[ http://issues.apache.org/jira/browse/DERBY-1409?page=comments#action_12416299 ]
Kristian Waagan commented on DERBY-1409: ---------------------------------------- Is this change required to run existing tests the way you want to, or are you writing new tests? I just want to point out that 'DerbyJUnitTest' is kind of deprecated. 'BaseJDBCTestCase' (or in rare cases 'BaseTestCase') should be used when writing new tests. > DerbyJUnitTest lacks String argument constructor > ------------------------------------------------ > > Key: DERBY-1409 > URL: http://issues.apache.org/jira/browse/DERBY-1409 > Project: Derby > Type: Improvement > Components: Test > Versions: 10.3.0.0 > Reporter: Michelle Caisse > Priority: Minor > Attachments: DerbyJUnitTest.patch > > With JUnit, a test can be executed on specified test methods by instantiating > a suite of (one or more) Tests of named test methods, as shown in this > snippet from the JUnit documentation: > public static Test suite() { > TestSuite suite= new TestSuite(); > suite.addTest(new MoneyTest("testMoneyEquals")); > suite.addTest(new MoneyTest("testSimpleAdd")); > return suite; > } > To support this method of specifying tests to be run, DerbyJUnitTest must > contain a constructor with a String argument that invokes the superclass > String arg constructor. -- 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
