[DERBY-5791] Replication tests should use BaseTestCase.execJavaCmd() to run local commands

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.10.1.1
• Fix Version/s: 10.10.1.1
• Component/s: Test
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 29/May/12 12:35
• Updated: 24/Jul/12 17:31
• Resolved: 30/May/12 10:59

Description

The replication tests invoke Runtime.exec() directly in order to spawn processes. The sub-processes that run on the same host as the main test process, should instead be started with the helper method BaseTestCase.execJavaCmd(). Having all the tests use the helper method would make it easier if we for example want to pass specific flags to all sub-processes created in a test run.

Note that the replication tests also have code for starting processes on a remote host via ssh. BaseTestCase.execJavaCmd() cannot do that, so only local processes can be started with the helper method. When the replication tests run as part of suites.All, all the spawned processes run locally.

Issue Links

• relates to: DERBY-5783 Remove duplicated code for starting remote processes in replication tests