[ 
https://issues.apache.org/jira/browse/DERBY-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Myrna van Lunteren updated DERBY-2446:
--------------------------------------

    Attachment: Derby-2446_1.diff
                Derby-2446_1.stat

I think the last few tests - junitTests/CompatibilityTest and 
derbynet/TestProtocol.java - have been converted. 
We were still running the CompatibilityTest both ways, though.

I'm attaching a patch which
- removes the references to the harness from TestConfiguration.java
  I left the assignment of DEFAULT_CONFIG=JUNIT_CONFIG, although now, there is 
only one configuration. But we may in future have something else?
- removes the junitTest/* directory altogether
- removes this junitTest/* from suites/derbynetclientmats.runall
- removes embeddedUseprocess.exclude
  (because it now no further purpose; all tests that were in it have been 
removed from derbyall).
- removes various (converted) tests that are no longer run through derbyall 
from DerbyNetClientUseprocess.exclude and DerbyNetRemote.exclude.

                
> 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
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to