[DERBY-2076] Rewrite junitTests/derbyNet/CompatibilityTest to conform to current JUnit usage

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.10.1.1
• Component/s: Test
• Assignee: Kristian Waagan
• Reporter: Samuel Andrew McIntyre
• Created: 13/Nov/06 23:54
• Updated: 21/Jan/15 00:23
• Resolved: 05/Oct/12 11:25

Description

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.

Issue Links

• blocks: DERBY-2446 Remove notion of the old test harness from TestConfiguration
• is related to: DERBY-5889 tests.compatibility._Suite has AccessControlException errors on Windows
• relates to: DERBY-6397 Run the rewritten compatibility test with multiple JVMs
• relates to: DERBY-1048 Include run of junitTests/CompatibilitySuite, or converted compatibility test suite with 10.1/trunk combination into suites.All
• requires: DERBY-5475 Formalize use of old Derby distributions in tests

Sub-Tasks

• Move assertDirectoryDeleted from BaseJDBCTestCase to BaseTestCase: Closed