db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-514) Integrate upgrade tests into test suite
Date Wed, 05 Apr 2006 19:06:44 GMT
     [ http://issues.apache.org/jira/browse/DERBY-514?page=all ]

Deepa Remesh updated DERBY-514:
-------------------------------

    Attachment: derby-514-patch2-runtest-v1.diff
                derby-514-patch2-runtest-v1.status

Attaching a patch 'derby-514-patch2-runtest-v1.diff' which enables the upgrade test to run
with the test harness. 

Summary:

* findCodeBase method in harness/jvm.java is changed to public. This method is used by upgrade
test to get the location of new jar files.

* Adds the other derby jars to the jar file list in UpgradeTester. This will allow the test
to run in client framework. I tried running the test in client framework and it looks like
this will need new master file and some more work.

* In UpgradeTester, File.toURL method is used when creating class loader. This seems to be
a better way to construct the URL.

* Master file update

This patch combined with the previous patch (derby-514-buildfiles-v1.diff) will allow the
upgrade test to be run using RunTest. The location of old jars has to be passed in as a property
in jvmflags. Command to run:
java -Djvmflags=-DderbyTesting.oldJarLocation=<location of 10.1 jars> org.apache.derbyTesting.functionTests.harness.RunTest
upgradeTests/Upgrade_10_1_10_2.java

I am working on making the build use a new property in ant.properties file and use it to generate
a property file for the test. As this work is not fully done, I am posting this interim patch.
Currently the upgrade test will run only with jar files. To be able to run with classes folder,
we will have to modify the metadata test in 10.1. Also, createClassLoader method will need
to be changed. 

I would appreciate if someone can look at the following patches which are waiting for review/commit:
* derby-514-buildfiles-v1.diff
* derby-514-patch2-runtest-v1.diff

> Integrate upgrade tests into test suite
> ---------------------------------------
>
>          Key: DERBY-514
>          URL: http://issues.apache.org/jira/browse/DERBY-514
>      Project: Derby
>         Type: Test

>   Components: Test
>     Versions: 10.1.2.0, 10.2.0.0
>     Reporter: Kathey Marsden
>     Assignee: Deepa Remesh
>      Fix For: 10.2.0.0
>  Attachments: derby-514-buildfiles-v1.diff, derby-514-buildfiles-v1.status, derby-514-patch1-v1.diff,
derby-514-patch1-v1.status, derby-514-patch2-runtest-v1.diff, derby-514-patch2-runtest-v1.status
>
> Currently there are no upgrade tests in the derbyAll suite.
> The upgrade tests java/testing/org/apache/derbyTesting are run by script and require
that the version to be tested by specified on the command line so that the classpath can be
changed.
> # runphases old_major old_minor old_engine new_engine
> #
> # e.g.
> #
> # runphases 10 0 c:/derby/10.0.2.1/lib c:/derby/trunk/jars/sane
> Perhaps this script can be rewritten in Java using class loaders and  previous Derby
verssions such as 10.0 and 10.1 be checked in so that this testing can   be incorporated into
the derbyAll test suite.

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


Mime
View raw message