db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5145) Provide option to limit compatibility test to combinations that include trunk
Date Mon, 06 Jun 2011 13:49:59 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044845#comment-13044845

Bryan Pendleton commented on DERBY-5145:

That seems quite sensible.

> 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:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: latestOnly.diff
> The compatibility test by default tests all possible client/server combinations. This
includes testing already released versions against each other, like client against 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

View raw message