Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <17333033.1160921975706.JavaMail.jira@brutus>
Date: Sun, 15 Oct 2006 07:19:35 -0700 (PDT)
From: "Deepa Remesh (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1689) Remove Upgrade_10_1_10_2 test from
 10.3 and add new upgrade tests for 10.3
In-Reply-To: <8752491.1155571393859.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1689?page=comments#action_12442394 ] 
            
Deepa Remesh commented on DERBY-1689:
-------------------------------------

Thanks Bryan for bringing this up. I see Yip has already submitted a patch for DERBY-630 with upgrade test for 10.1 to 10.3. Thanks Yip.  And as Yip mentioned, for testing upgrade from 10.2 to 10.3, we will need to check in the 10.2 jars. 

As we now have the 10.2 release jars available, it would be good if we can get it into svn similar to what was done for 10.1 jars. Andrew had done this for 10.1 here: http://issues.apache.org/jira/browse/DERBY-1049
And then we can add the upgrade test for 10.2 to 10.3 which should resolve this issue.


> Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
> --------------------------------------------------------------------------
>
>                 Key: DERBY-1689
>                 URL: http://issues.apache.org/jira/browse/DERBY-1689
>             Project: Derby
>          Issue Type: Task
>          Components: Test, Regression Test Failure
>    Affects Versions: 10.3.0.0
>            Reporter: Deepa Remesh
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: remove_10_2_upg_test.diff
>
>
> The current upgrade test Upgrade_10_1_10_2 tests upgrade from 10.1 to 10.2. This test should continue to run in 10.2 branch. It is failing in the new trunk (10.3) because the test internally checks the versions. To resolve this failure, we should remove this test from running in new trunk and then create new upgrade tests to test new upgrade scenarios: 
> * 10.1 to 10.3
> * 10.2 to 10.3
> Upgrade test uses the UpgradeTester class which contains the test for various upgrade scenarios. To test any old/new release upgrade combination, we can create a new test which uses this class and pass in the old and new versions to the class. Any new upgrade scenarios for new features can be added to UpgradeTester (e.g, test for 10.2 feature grant/revoke was added to UpgradeTester).

-- 
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