Thanks, Rick. Can you add a comment with the SVN revision number of your sandbox? This helps me merge the patch into the right snapshot of the codeline.

David

Rick Hillegas (JIRA) wrote:
     [ http://issues.apache.org/jira/browse/DERBY-516?page=all ]

Rick Hillegas updated DERBY-516:
--------------------------------

    Attachment: bug516.diff

Hi, David: I have amended this patch as you suggested. I ran derbyall and one 
test failed: dataSourcePermissions_net. When I ran derbynetmats by itself, this 
test passed so I'm writing it off as some kind of environmental hiccup. The 
files in this amended submission are:

M      tools\ant\properties\compilepath.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
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
A      
java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUnitTest.java
M      java\testing\build.xml
M      java\client\org\apache\derby\client\net\Reply.java
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: 10.1.1.0
   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/


begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard

Reply via email to