[
https://issues.apache.org/jira/browse/DERBY-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464054
]
Myrna van Lunteren commented on DERBY-2217:
-------------------------------------------
I generally like the new approach.
I have some small concerns though.
1. This test presumably relies on the new changes to support junit tests...And
thus it is not applicable for 10.2 branch.
Where does that leave us for the 10.2 branch? Is it acceptable to continue
automated runs there with an upgrade from 10.1.1.0 to 10.2.(latest)?
I tried to use derbyTesting.jar with the new tests, and 10.2.2.0 derby.jar
to see if that was an approach that would work, but I get errors.
2. I noticed the automatic specification of the jarlocation (done in
upgradeTests/build.xml via a _app file) has been dropped. I think that's ok -
but it assumes we will have to run suites.All with the new property passed in,
or the upgrade tests will get skipped.
> Convert upgrade tests to Junit
> ------------------------------
>
> Key: DERBY-2217
> URL: https://issues.apache.org/jira/browse/DERBY-2217
> Project: Derby
> Issue Type: Improvement
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> Also support running against multiple old versions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
