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] [Commented] (DERBY-5145) Provide option to limit compatbility test to combinations that include trunk
Date Tue, 22 Mar 2011 13:50:05 GMT

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

Knut Anders Hatlen commented on DERBY-5145:
-------------------------------------------

This can almost be achieved with the current options.

If you have a compatibilitytest.properties file set up with the following Derby versions

derby.versions=18
derby.version0=10.0.2.1
...
derby.version17=Trunk

you can limit it to only use the client from trunk by adding the line

test.singleClient=17

Then you'll test the client from trunk against all server versions.

Similarly, you can test all client versions against the server from trunk by using the property
test.singleServer instead of test.singleClient.

This approach however requires you to run the compatibility tests twice, with two different
derbycompatibilitytest.properties configuration files. It would have been better if we had
a property that enabled you to test the same set of combinations in a single invocation.

> Provide option to limit compatbility 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.0.0
>            Reporter: 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

Mime
View raw message