[
https://issues.apache.org/jira/browse/DERBY-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204813#comment-13204813
]
Kristian Waagan commented on DERBY-2076:
----------------------------------------
Yes, there is more work forthcoming.
I ended up being out for several months when I was working on this, so I'll
have to restart the effort. There are more related changes going in.
In any case, I think it will be good to sort out the existing issues before I
do more on this issue - some of the changes are substantial (but should only
affect specific test groups, like the CompatibilityTest and the UpgradeTest).
This is part of getting rid of the very first JUnit framework code we wrote.
I'll add a link to the other relevant issue(s) later.
> 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: 10.3.1.4
> Reporter: Andrew McIntyre
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-2076-0a-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
