[ https://issues.apache.org/jira/browse/DERBY-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-2446. --------------------------------------- Resolution: Fixed Fix Version/s: 10.11.0.0 Assignee: Myrna van Lunteren Issue & fix info: Newcomer (was: Newcomer,Patch Available) I'm resolving this issue, I think now all references to the old (10.1, 10.2?) junit tests are removed from TestConfiguration. > Remove notion of the old test harness from TestConfiguration > ------------------------------------------------------------ > > Key: DERBY-2446 > URL: https://issues.apache.org/jira/browse/DERBY-2446 > Project: Derby > Issue Type: Task > Components: Test > Affects Versions: 10.3.1.4 > Reporter: Kristian Waagan > Assignee: Myrna van Lunteren > Priority: Minor > Labels: derby_triage10_11 > Fix For: 10.11.0.0 > > Attachments: Derby-2446_1.diff, Derby-2446_1.stat > > > TestConfiguration has a notion of the old test harness. It is used when the > old harness is running JUnit tests, and differs mostly by reading the system > properties set by the harness and propagating these to the test configuration. > I found only one JUnit test being run from the harness; LobStreamsTest.junit. > However, this is also run by the JUnit suite jdbcapi. > My suggestion is to remove the code related to the old harness in > TestConfiguration and disable LobStreamsTest in derbynetclientmats. > A quick test showed that only LobStreamsTest failed when removing all the > relevant code in TestConfiguration (ran both derbyall and suites.All). -- This message was sent by Atlassian JIRA (v6.1#6144)