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

Derby

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

Created: 29/Apr/09 06:54 PM Updated: 04/Aug/09 12:43 AM

Component/s:

Test

Affects Version/s:

10.5.2.0, 10.6.0.0

Fix Version/s:

10.5.3.0, 10.6.0.0

Time Tracking:

Not Specified

File Attachments:

File Name	Date Attached	Attached By	Size
Derby-4203.diff	2009-07-17 05:26 PM	Lily Wei	4 kB
derby-4203.diff	2009-07-06 02:22 PM	Lily Wei	2 kB

Resolution Date:	04/Aug/09 12:43 AM
Labels:

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permalink | « Hide ]

Lily Wei added a comment - 06/Jul/09 02:22 PM

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.

[ Permalink | « Hide ]

Lily Wei added a comment - 17/Jul/09 05:26 PM

Thanks for Kathey to look at this patch that is first post on Derby-4166. I make the changes for the typo. I also do the diff from the top. And, this change only apply for mailjdbc tests.

[ Permalink | « Hide ]

Kathey Marsden added a comment - 17/Jul/09 06:12 PM

Thanks Lily. I committed the mailjdbc patch to trunk and 10.5