db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-514) Integrate upgrade tests into test suite
Date Tue, 28 Mar 2006 16:21:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-514?page=comments#action_12372117 ] 

Rick Hillegas commented on DERBY-514:

Hi Deepa,

I think it would be OK for the testing instructions in README.htm to say something like the

o You have to create a properties file which says where the old jars live.

o You have to make that properties file visible on your classpath.

If the upgrade test can't find the properties file, then it can error out with a diagnostic
which tells the user how to correct the problem. For extra credit, the build script could
generate this properties file in a canonical place (and the clobber target could delete it).
If you go down that route, I would recommend against generating the file in the compiled classtree--I
don't think you want environment-specific cruft finding its way into the standard jars.

Just a suggestion...


> 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-patch1-v1.diff, derby-514-patch1-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