[ https://issues.apache.org/jira/browse/DERBY-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480118 ]
Kristian Waagan commented on DERBY-2446: ---------------------------------------- Thanks for the information. Is the current test in the old harness broken, or does it actually work because the test is run in a separate process? Either way, I plan to make the suggested changes since we are aiming to "kill the old harness". If anyone feel this is something we should investigate further, please create a separate Jira for it. thanks, > 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.0.0 > Reporter: Kristian Waagan > Assigned To: Kristian Waagan > Priority: Minor > > 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 is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.