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 Thu, 11 May 2006 16:25:06 GMT
     [ http://issues.apache.org/jira/browse/DERBY-514?page=all ]

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

    Attachment: derby-514-runwithclasses.diff
                derby-514-runwithclasses.status

Attaching a patch 'derby-514-runwithclasses.diff' which enables upgrade suite to run with
classes folder. This patch will resolve this issue fully. This patch adds upgrade suite to
derbyall and also removes the previous upgrade test folder which is not used now.

Initially, I had thought the following to be an issue when running with classes folder: 
"Currently, we are using the test classes (derbyTesting.jar) from new version in all cases.
This separation is not possible when we use classes folder." 

Now, I have added the whole classes folder from new version at the end of search path of the
old class loader. This means any classes which are added in the new version but not present
in the old version will be available to the old class loader. This may limit testing certain
upgrade features. However, this will be caught by running the test with jar files where we
have a clear separation.

With this patch, I ran the upgrade suite with both sane jars and classes. I also ran derbyall
with classes and checked that upgrade test passes. Tests run with Sun JDK1.4.2 on Windows
XP. 

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: 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,
derby-514-patch3-v1.diff, derby-514-patch3-v1.status, derby-514-patch3-v2.diff, derby-514-patch3-v2.status,
derby-514-patch4-sed.diff, derby-514-patch4-sed.status, derby-514-patch5-addtoderbyall.diff,
derby-514-patch5-addtoderbyall.status, derby-514-patch6-build_changes.diff, derby-514-patch6-build_changes.status,
derby-514-patch7-andrew.diff, derby-514-patch7-v2.diff, derby-514-runwithclasses.diff, derby-514-runwithclasses.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