db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-516) Need to incorporate client backward/forward compatibility testing into testing procedures.
Date Tue, 25 Oct 2005 02:02:57 GMT
     [ http://issues.apache.org/jira/browse/DERBY-516?page=all ]

Rick Hillegas updated DERBY-516:

    Attachment: bug516.diff

Incorporate Andrew's suggestion:

1) Amended BUILDING.txt and README.htm.

2) Moved junit jar symbol from compilepath to extrapath and adjusted build files accordingly.

3) Eliminated vacuous Reply.java

Contents of new patch:

M      tools\ant\properties\extrapath.properties
M      java\build\org\apache\derbyBuild\build.xml
M      java\testing\README.htm
A      java\testing\org\apache\derbyTesting\functionTests\tests\compatibility
A      java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\README.html
A      java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\testScript.xml
A      java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\Pinger.java
A      java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\JDBCDriverTest.java
A      java\testing\org\apache\derbyTesting\functionTests\tests\compatibility\build.xml
A      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\build.xml
A      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\CompatibilityTest_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\copyfiles.ant
M      java\testing\org\apache\derbyTesting\functionTests\harness\Sed.java
A      java\testing\org\apache\derbyTesting\functionTests\master\CompatibilityTest.out
M      java\testing\org\apache\derbyTesting\functionTests\suites\derbynetmats.runall
M      java\testing\org\apache\derbyTesting\functionTests\util\build.xml
A      java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUnitTest.java
M      java\testing\build.xml
M      BUILDING.txt
M      build.xml

> Need to incorporate client backward/forward  compatibility testing into testing procedures.
> -------------------------------------------------------------------------------------------
>          Key: DERBY-516
>          URL: http://issues.apache.org/jira/browse/DERBY-516
>      Project: Derby
>         Type: Test
>   Components: Test
>     Versions:
>     Reporter: Kathey Marsden
>     Assignee: Rick Hillegas
>  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.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message