db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-2076) Rewrite junitTests/derbyNet/CompatibilityTest to conform to current JUnit usage
Date Wed, 27 Jun 2012 15:08:45 GMT

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

Kristian Waagan commented on DERBY-2076:

FYI, here's the number of combinations computed for the various suites, including
and excluding [1]:
 o _Suite: 19
 o _SuiteDevFull: 39
 o _SuiteOld: 100
 o _SuiteOldFull: 400

These numbers include combinations where client X is tested against server X.

[1] is excluded because it doesn't have a client driver. The old/current test uses
the client from the closest newer Derby-version instead, but I don't see the point in that.
In fact, I'm considering adding a cutoff value, such that we ignore all versions older than
a given version by default.
> Rewrite junitTests/derbyNet/CompatibilityTest to conform to current JUnit usage
> -------------------------------------------------------------------------------
>                 Key: DERBY-2076
>                 URL: https://issues.apache.org/jira/browse/DERBY-2076
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions:
>            Reporter: Andrew McIntyre
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-2076-0a-modernized_compat_test_preview.diff, derby-2076-0b-modernized_compat_test_preview.diff,
> The test org.apache.derbyTesting.functionTests.tests.junitTests.DerbyNet.CompatibilityTest
has been failing in the nightlies because it needs to be run in the old test harness, and
for some reason the property which grants permission to read ${user.home}/junit.properties
is not being picked up properly in the old harness. 
> I am able to resolve the problem by granting permission to read ${user.home}/junit.properties
to all, but the test should be refactored so that it can run with the rest of the junit tests
without needing the old harness.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message