You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mike Matrigali (JIRA)" <de...@db.apache.org> on 2006/04/12 01:05:20 UTC

[jira] Updated: (DERBY-1048) Include run of jdbcapi/Compatibility test with first client release into derbyall

     [ http://issues.apache.org/jira/browse/DERBY-1048?page=all ]

Mike Matrigali updated DERBY-1048:
----------------------------------

    Component: Test

> Include run of jdbcapi/Compatibility test with first  client release into derbyall
> ----------------------------------------------------------------------------------
>
>          Key: DERBY-1048
>          URL: http://issues.apache.org/jira/browse/DERBY-1048
>      Project: Derby
>         Type: Sub-task

>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Kathey Marsden

>
> Incorporate a run of jdbcapi/Compatibility test into derbyall  with the following combinations:
> client                server
> 10.1.1.0           trunk
> trunk                10.1.1.0
> This can provide some minimal compatibility testing in derbyall against the original client release.
> It requires that the 10.1.1.0 jars be checked in.  I will file a separate issue for this.
> Rick is assigned to the top level issue to integrate testing procedures.   He wrote the test but there was concern that we actually not adding any coverage for compatibilty because it only runs with trunk server/ trunk client.
> Adding this combination was discussed in this thread.
> http://www.nabble.com/Question-about-client-compatibility-testing-and-DERBY-516-%28paging-Rick-%3A%29%29-t506203.html#a1372016

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira