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] [Updated] (DERBY-2076) Rewrite junitTests/derbyNet/CompatibilityTest to conform to current JUnit usage
Date Tue, 31 Jul 2012 06:58:34 GMT

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

Kristian Waagan updated DERBY-2076:

    Attachment: derby-2076-2a-enable_test.diff

Attached patch 2a, which enables the test in suites.All.

Since I haven't gotten any feedback on testing, I've decided to enable the test and see what
happens :)

If you don't have the old releases in the default location, and don't specify derbyTesting.oldReleasePath,
you may see an ALARM statement printed to the console.
The test doesn't require any specific versions, it will test with whatever old versions of
Derby that are made available. This is different from some other tests.

Committed patch 2a to trunk with revision 1367428.
> 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: compiler-level.patch, derby-2076-0a-modernized_compat_test_preview.diff,
derby-2076-0b-modernized_compat_test_preview.diff, derby-2076-1a-initial.diff, derby-2076-1b-initial.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