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 "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2011/06/06 13:47:58 UTC

[jira] [Assigned] (DERBY-5145) Provide option to limit compatibility test to combinations that include trunk

     [ https://issues.apache.org/jira/browse/DERBY-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen reassigned DERBY-5145:
-----------------------------------------

    Assignee: Knut Anders Hatlen

> Provide option to limit compatibility test to combinations that include trunk
> -----------------------------------------------------------------------------
>
>                 Key: DERBY-5145
>                 URL: https://issues.apache.org/jira/browse/DERBY-5145
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.8.1.2
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>
> The compatibility test by default tests all possible client/server combinations. This includes testing already released versions against each other, like 10.6.2.1 client against 10.1.2.1 server. Testing for incompatibilities between already released versions isn't of much interest for the ongoing development. For example, when testing a change on trunk, you're really only interested in the combinations that have trunk either on the server side or on the client side. If we could filter out the combinations that didn't test any code on trunk (or some other branch we want to test), the time to run the tests could be significantly reduced.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira