Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1742594229.1142981174959.JavaMail.jira@ajax>
Date: Tue, 21 Mar 2006 22:46:14 +0000 (GMT)
From: "Deepa Remesh (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-1075) Combine the script and the test
 available for upgrade testing into a java test
In-Reply-To: <835491823.1141421739814.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]

Deepa Remesh updated DERBY-1075:
--------------------------------

    Attachment: derby-1075-v1.diff
                derby-1075-v1.status

Attaching a patch 'derby-1075-v1.diff'. This patch is based on the draft patch with some additional changes.

Summary of patch:

1. Creates a class UpgradeTester which does the following:

* Creates two class loaders using the jar locations provided for old and new release
* Switches between these two class loaders to run the different upgrade phases with old or new release.
* This class can be used to write tests for upgrades from different releases.

2. Adds a new test Upgrade_10_1_10_2 which uses UpgradeTester to test upgrade from 10.1 to 10.2. This test has not been added to any suite. Till the jars from previous release are available in svn, the test has to be run manually using the command:
java Upgrade_10_1_10_2 <location of old jars> <location of new jars>
e.g, java Upgrade_10_1_10_2 C:\derby\10.1\lib C:\derby\trunk\lib

Also, there are some issues in running the test using the harness because of use of security manager. These are mentioned in http://www.nabble.com/Upgrade-test-and-security-permissions-p3517019.html. Any suggestions to resolve these are welcome. I am planning to open separate sub-task for making this test run with a security manager.

3. Creates a new package upgradeTests under org.apache.derbyTesting.functionTests.tests. This package is for UpgradeTester class and the individual upgrade tests.

4. Adds a master 'Upgrade_10_1_10_2.out'. I have tried to reduce the diffs by doing version check in the code and removing reference to local machine paths. Still, there are few more diffs. I am planning to look at these once this patch is reviewed/committed.

This patch only adds new files. I verified that build is successful and I can run the new test. I would appreciate if someone can take a look at this patch and review/commit it.

> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
>          Key: DERBY-1075
>          URL: http://issues.apache.org/jira/browse/DERBY-1075
>      Project: Derby
>         Type: Sub-task
>     Reporter: Deepa Remesh
>     Assignee: Deepa Remesh
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: derby-1075-patch1-draft.diff, derby-1075-patch1-draft.status, derby-1075-v1.diff, derby-1075-v1.status, loader.java, loader_v2.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine the script 'runphases.ksh' and the java file 'phaseTester.java' into a single java test. This will help to later add the upgrade tests into the regression suite. Also, this sub-task can be done independent of DERBY-1049 which is blocking DERBY-514.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira