[
https://issues.apache.org/jira/browse/DERBY-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-2446:
-----------------------------------
Assignee: (was: Kristian Waagan)
Thanks Dan. I notcied this when I ran the tests with Java 1.6.
I think AutoloadBooting will be the most difficult one to fix. I guess we could
live with moving LobStreamsTests, even though we might loose some testing
coverage. I see an issue has been filed for rewriting the ComatibilityTest.
I don't have the time to work on any of the related issues now, so I'm
unassigning myself. Hopefully enough information has been collected for someone
to pick this up later.
> 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
> 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.
