[ http://issues.apache.org/jira/browse/DERBY-514?page=comments#action_12358408 ]
Kathey Marsden commented on DERBY-514: -------------------------------------- I think that this will require that previous versions of Derby be checked into the codeline. Then the tests will access the databases with the various versions. I am not sure the best location for the jars to live. Previous versions would be also be good to have for other tests such as client/server compatiblity tests. Also before rewriting these tests I think it would be good to have the base upgrade infrastructure for 10.2. I'll log a Jira isssue for that. > 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 > Fix For: 10.2.0.0 > > 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
