[
https://issues.apache.org/jira/browse/DERBY-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner resolved DERBY-1689.
------------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 10.3.0.0)
I believe that this should be handled by the conversion of the upgrade testing
to JUnit described in DERBY-2217
> Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
> --------------------------------------------------------------------------
>
> Key: DERBY-1689
> URL: https://issues.apache.org/jira/browse/DERBY-1689
> Project: Derby
> Issue Type: Task
> Components: Regression Test Failure, Test
> Affects Versions: 10.3.0.0
> Reporter: Deepa Remesh
> Priority: Minor
> 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:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
