[ http://issues.apache.org/jira/browse/DERBY-1076?page=comments#action_12370779 ]
Deepa Remesh commented on DERBY-1076: ------------------------------------- Kathey, I agree that we should be able to run upgrade tests to check that upgrade does not have problems before 10.2 is released. I am continuing the effort put into upgrade test by Mamta, Dan and others and trying to make it run as part of derbyall. Currently, I think it is difficult to test the upgrade mainly because of two things: * Test is not part of derbyall. We have to run the test and compare the master files manually. * Running manually is also a problem because of the existing diffs in the master file >From what I have seen, the diffs are caused by following: * Failure in DatabaseMetadata.getColumnPrivileges (DERBY-1121). Because of this, metadata test does not run to completion after soft upgrade. Maybe, as a test, we should modify the metadata test to ignore this exception and run the test after soft upgrade. This is just to make sure there are no other problems further along the test. I'll try this. * Master updates in metadata test not reflected in phaseTester.out. The major part of phaseTester.out is the output of metadata test. After each phase, metadata test is run. phaseTester.out has to be updated to reflect the changes which have happened in the meantime. * The master file is created with version 10.1.2.2. If we run the test with another version say, 10.1.2.4, there will be diffs. It will be good to avoid version information in the master file and do the necessary checking inside the test itself. I am working on this in DERBY-1075. * Some machine specific locations in the file. We can avoid printing this to the output. I am doing this is DERBY-1075. Proposal: I have a draft patch attached to DERBY-1075 and would appreciate feedback on it. This patch creates a java class which can be used to write upgrade tests. Once this patch is reviewed and okay, we can then proceed to create upgrade tests. This should allow anybody to run the tests using the test harness. Once the output differences are resolved, we can add the tests to a suite and make it part of derbyall run. Does this sound reasonable? > Resolve the ouput differences in upgrade test > --------------------------------------------- > > Key: DERBY-1076 > URL: http://issues.apache.org/jira/browse/DERBY-1076 > Project: Derby > Type: Sub-task > Components: Test, Regression Test Failure > Reporter: Deepa Remesh > Priority: Minor > Fix For: 10.2.0.0 > Attachments: derby-1076_metadata_test.diff, phaseTester.diff, phaseTester.out > > The output of running the upgrade test script (runphases.ksh) differs from > what is checked into the master file > (java\testing\org\apache\derbyTesting\functionTests\master\phaseTester.out). > These differences need to be checked to see there are no real issues in the > upgrade itself. -- 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
