db-derby-dev mailing list archives

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

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

Knut Anders Hatlen updated DERBY-5145:
--------------------------------------

    Attachment: latestOnly.diff

Attaching a patch that adds a new flag, test.latestOnly, which can be set in compatibilitytest.properties
in order to limit the testing to combinations that use the latest version either on the client
side or on the server side.

If you run the compatibility tests with all official releases (18 versions currently) + trunk,
using a single JVM version, the number of combinations that are tested will drop from 361
(N²) to 37 (2N-1) when the property is set. In other words, the number of combinations grows
linearly with the number of Derby versions instead of quadratically. (The number of combinations
still grows quadratically with the number of JVM versions, though.)

> 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
>         Attachments: latestOnly.diff
>
>
> 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

Mime
View raw message