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 Fri, 07 Apr 2006 01:05:29 GMT
     [ http://issues.apache.org/jira/browse/DERBY-514?page=all ]

Deepa Remesh updated DERBY-514:

    Attachment: derby-514-patch3-v1.diff

Kathey, Thanks for committing the previous patches. I have noted your concern about error
reporting but not yet made that change in this next patch. 

'derby-514-patch3-v1.diff' patch changes the build script to use a property which points to
the location of old jars. With this change, it should be possible to run the upgrade test
using RunTest without any additional command-line flags. It requires a property to be set
in ant.properties which will be used at build time.


* Changes the build to use a property derbyTesting.jar.path and use it's value for the location
of the jar files from previous release. This property has to be set in ant.propeties and is
optional. It is required to run the upgrade tests.

* Updates building.txt with the information about new property

* During build, the new property will be read and used to set the property in the test properties
file. Currently, it sets a property in Upgrade_10_1_10_2_app.properties. This needs to be
generalized as more upgrade combinations will be tested. But I am having trouble doing it
in a separate property file as it does not get loaded by harness. I will continue to look
into this.

* Changes UpgradeTester to use the new property. UpgradeTester finds out the location of old
and new jars and hence these need not be passed into the class.

I ran the upgrade test with and without setting "derbyTesting.jar.path" property and it works
as expected. I have not yet tried with Andrew's changes for derby-1049. 

Please take a look at this patch. Thanks.

> 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:,
>     Reporter: Kathey Marsden
>     Assignee: Deepa Remesh
>      Fix For:
>  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,
derby-514-patch3-v1.diff, derby-514-patch3-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
> # runphases old_major old_minor old_engine new_engine
> #
> # e.g.
> #
> # runphases 10 0 c:/derby/ 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:
For more information on JIRA, see:

View raw message