[
https://issues.apache.org/jira/browse/DERBY-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103684#comment-13103684
]
Kristian Waagan commented on DERBY-2446:
----------------------------------------
When running derbyall, this test failed when I added code to throw an exception
when TestConfiguration ended up with the harness config:
derbyall/derbynetclientmats/derbynetclientmats.fail:derbynet/testProtocol.java
See DERBY-2031.
I didn't run the compatibility test, so it may be dependent on the harness code
in TestConfiguration still.
> 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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
