[
https://issues.apache.org/jira/browse/SQOOP-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243694#comment-14243694
]
Abraham Elmahrek commented on SQOOP-1783:
-----------------------------------------
This don't apply any more [~jarcec], could you update the patch?
> Sqoop2: Create derby integration upgrade tests
> ----------------------------------------------
>
> Key: SQOOP-1783
> URL: https://issues.apache.org/jira/browse/SQOOP-1783
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.4
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.5
>
> Attachments: SQOOP-1783.patch, SQOOP-1783.patch,
> TEST-org.apache.sqoop.integration.repository.derby.upgrade.Derby1_99_4UpgradeTest.xml,
> derby-repository-1.99.4.tar.gz, sqoop.log, tomcat.log
>
>
> During my validation of 1.99.4 release, I've several times run upgrade
> scenario when I took repository generated by previous release and let the new
> release upgrade the structures. We've found several bugs during this manual
> exercise as we did several changes and we don't have any test coverage in
> this area. Hence for future releases I would like to introduce automatic
> upgrade tests that would run as a part of our integration test suite.
> I'm currently thinking of doing exactly what I've done in my manual exercise.
> We can create example derby repository that is exercising various different
> values for (all) previous releases and store that an archive with the code.
> The integration tests will then untar the stored archive and simply run the
> upgrade procedure This approach won't guarantee that we will catch all
> upgrade bugs, but will provide reasonable confidence that we can release the
> new bits without additional manual testing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
