[
https://issues.apache.org/jira/browse/DERBY-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-516:
--------------------------------
Issue Type: Improvement (was: Test)
> Need to incorporate client backward/forward compatibility testing into
> testing procedures.
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-516
> URL: https://issues.apache.org/jira/browse/DERBY-516
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.1.1.0
> Reporter: Kathey Marsden
> Attachments: bug516.diff
>
>
> Need to incorporate client backward/forward compatibility testing into
> testing procedures.
> New versions of the Derby network server should work with old versions of the
> network client. New versions of the Derby network client should work with
> old versions of the server. Currently that means that the 10.1 client should
> be tested on the trunk. The 10.2 client definitely needs to be tested
> with the 10.1 server before release, but it would be good to start testing
> snapshots of 10.2 client on the 10.1 branch earlier.
>
> Note:
> Bug fixes may mean that the canons differ for different versions.
> The test harness I think is set up to allow different masters for different
> versions. It at least has that functionality for the DerbyNet framework
> and it could be expanded to cover DerbyNetClient. The way it works is that
> the harness checks for a masters in the following order:
> functionTests/master/<framework>/ver<version>
> functionTests/master/<framework>/
> functionTests/master/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
