Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <10857028.1170880026829.JavaMail.jira@brutus>
Date: Wed, 7 Feb 2007 12:27:06 -0800 (PST)
From: "Andrew McIntyre (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2305) Convert tests in derbynet that will
 run via HarnessJavaTest
In-Reply-To: <6211457.1170880025535.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew McIntyre updated DERBY-2305:
-----------------------------------

    Attachment: derby-2305-v1.diff

> 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.