db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-2305) Convert tests in derbynet that will run via HarnessJavaTest
Date Thu, 15 Feb 2007 23:07:07 GMT

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

Andrew McIntyre closed DERBY-2305.
----------------------------------

    Resolution: Fixed
    Derby Info:   (was: [Patch Available])

Committed patch and removed the tests that run in NetHarnessJavaTest from the old harness.
Will investigate converting BadConnectionTest into a more generic driver test later.

> Convert tests in derbynet that will run via HarnessJavaTest
> -----------------------------------------------------------
>
>                 Key: DERBY-2305
>                 URL: https://issues.apache.org/jira/browse/DERBY-2305
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Andrew McIntyre
>         Assigned To: Andrew McIntyre
>            Priority: Trivial
>             Fix For: 10.3.0.0
>
>         Attachments: derby-2305-v1.diff
>
>
> I was able to convert three tests in derbynet to run via HarnessJavaTest. The problems
with the other tests are mentioned in the javadoc for the test. Forking the VM seemed to be
a problem in most cases, at least running from within Eclipse, because the forked VM would
not have the correct classpath. Attaching patch for review. Note that BadConnectionTest is
commented out in _Suite in this patch, as I have a separate patch for converting the very
simple bad connection test.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message