Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 87638 invoked from network); 23 Nov 2005 19:42:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Nov 2005 19:42:01 -0000 Received: (qmail 23794 invoked by uid 500); 23 Nov 2005 19:42:00 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 23777 invoked by uid 500); 23 Nov 2005 19:42:00 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 23754 invoked by uid 99); 23 Nov 2005 19:42:00 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Nov 2005 11:41:58 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 27A34239 for ; Wed, 23 Nov 2005 20:41:37 +0100 (CET) Message-ID: <1150322863.1132774897160.JavaMail.jira@ajax.apache.org> Date: Wed, 23 Nov 2005 20:41:37 +0100 (CET) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-514) Integrate upgrade tests into test suite In-Reply-To: <1226651007.1124370240578.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ 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