You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Lily Wei (JIRA)" <ji...@apache.org> on 2009/07/06 16:22:15 UTC
[jira] Updated: (DERBY-4203) Change mailjdbc and sstest system
tests to be able to restart with the existing database instead of creating
a new one so they can be used for upgrade testing
[ https://issues.apache.org/jira/browse/DERBY-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lily Wei updated DERBY-4203:
----------------------------
Attachment: derby-4203.diff
This is the first attempt to fix this problem. I add a second argument to indicate we don't want to create a new database. This fixed will be the same for 10.5 and trunk. Note: I did not handle schema.sql and avoid recreate Activity.out or performance.out. The test will reuse data in mailsdb database. So, it can test soft upgrade from various release is working.
> Change mailjdbc and sstest system tests to be able to restart with the existing database instead of creating a new one so they can be used for upgrade testing
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4203
> URL: https://issues.apache.org/jira/browse/DERBY-4203
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.5.1.2, 10.6.0.0
> Reporter: Kathey Marsden
> Priority: Minor
> Attachments: derby-4203.diff
>
>
> It would be nice to have the system tests be able to pick up with an existing database instead of creating a new one, so they can be used for soft upgrade and hard upgrade testing after running a while with the old version.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.