[DERBY-2419] Tighten encapsulation of state in TestConfiguration

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.7.1.1
• Component/s: Test
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 08/Mar/07 10:09
• Updated: 29/Nov/10 14:21
• Resolved: 17/Jun/10 10:25

Description

Parts of the state of TestConfiguration has been made public, which they should not be; DEFAULT_PORT and DEFAULT_HOSTNAME.
Using these directly from the outside can cause settings overridden by the user to be ignored by tests. Further, a test should not care if the host/port it uses is the Derby default or the values set by the user running the test.

To obtain a hostname and a port number, use the methods getPort and getHostName in TestConfiguration.

Issue Links

• is related to: DERBY-4217 Make the default port for the suites.All run configurable with a system property.
• relates to: DERBY-4090 Provide the ability to run tests concurrently on the same machine