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 Tue, 28 Mar 2006 00:48:27 GMT
     [ http://issues.apache.org/jira/browse/DERBY-514?page=all ]

Deepa Remesh updated DERBY-514:

    Attachment: derby-514-patch1-v1.diff

Attaching a patch 'derby-514-patch1-v1.diff'. In the patch, I am trying to make the upgrade
test run with "RunTest" in the test harness. I do not have a full solution for this yet and
would appreciate any suggestions.

Patch does the following:
* Adds a property file with "noSecurityManager=true" because the upgrade test will require
more permissions. A sub-task is open to make the test run with security manager.

* Adds a sed file to sed out version information as the version is checked in the code itself.

* Adds copyfiles.ant and a build file to allow copying of the new files. Also modifies testing/build.xml
to include building of upgrade tests.

* Modifies the master file UpgradeTest.out to remove all diffs.

* As RunTest does not allow taking parameters, I have used place holders (<LOCATION_OF_OLD_JARS>
and <LOCATION_OF_NEW_JARS>) for the location of new and old jars in the test Upgrade_10_1_10_2.java
 To run the test, these variables has to be changed to the location on the local machine.
I am not comfortable with this solution and I am continuing work to avoid this. I had tried
to pass these as propeties in jvmflags to the test harness but harness has problems with multilple
properties in jvmflags. So here is what I am planning to do: 

- For new jars, I think we can get the location of jars from the classpath from which the
test is run. This is currently done in the jvm class when tests are run with security manager.
I am trying to see if I can use this existing code in some way. 

- For old jars, they are planned to be checked into svn as part of DERBY-1049 and they will
be avaialble in the svn workspace. But I do not know how the relative location of these jars
can be obtained when running tests. Will these jars be included in the testing build ? Any
ideas how else this can be done?

Some related things I am working on:
* Make the upgrade test run with classes folder in addition to the jars
* Do not depend on the new version. Upgrade_10_1_10_2.java may not be useful once we branch
out to 10.3. So I am trying to see if I can make the test not dependent on the new version.

With this patch, the test Upgrade_10_1_10_2.java runs cleanly. But the test cannot be run
directly without replacing the place holders in the code to point to the old and new version
jar locations on the local machine. I would appreciate any suggestions to proceed with this

> 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