Thanks for this important effort, Deepa.
Is there a document for developers somewhere that explains the kinds of
changes that impact upgrade, and how you go about writing a test an
upgrade-impacting change? I'm a bit mystified myself right now...
(although I'm pretty darn sure i18n changes in the client don't impact
upgrade :) ).
David
Deepa Remesh wrote:
Hi,
I have been working on making the upgrade tests run as part of
derbyall and noticed that there is only one test
(caseReusableRecordIdSequenceNumber) which has been specifically added
for 10.2. The javadoc comment for UpgradeTester class lists what is
tested for 10.1. I think we need a similar list for 10.2 and maybe,
more tests for any new features.
Andrew mentioned he is working on getting the jars in the repository
and I am working on using these repository jars and defining a
standard way to run the test so that it can run as part of derbyall.
I plan to document this in readme/building.txt once everything is in
place. For now, to run upgrade tests, we need to pass in the location
of previous version jar (10.1.2.1) as follows:
java -Djvmflags=-DderbyTesting.oldJarLocation=<location of 10.1 jars>
org.apache.derbyTesting.functionTests.harness.RunTest
upgradeTests/Upgrade_10_1_10_2.java
NOTE: Test runs with jar files in the classpath. It does not run with
classes folder.
Please feel free to add more 10.2 tests to UpgradeTester while rest of
the testing infrastructure is being set up.
Thanks,
Deepa
