[ http://issues.apache.org/jira/browse/DERBY-1689?page=comments#action_12442302 ] Bryan Pendleton commented on DERBY-1689: ----------------------------------------
Deepa, does this issue need to be addressed prior to committing any new trunk changes which include update functionality? For instance, there is a patch to DERBY-630 ready for commit. Will committing that patch complicate 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
