[TAP5-2180] SeleniumTestCase assumes that Selenium Server runs on the default port

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.3.7
• Fix Version/s: 5.4
• Component/s: tapestry-test
• Assignee: Howard Lewis Ship
• Reporter: Joachim Sauer
• Created: 12/Sep/13 06:13
• Updated: 05/Nov/13 00:25
• Resolved: 04/Nov/13 22:45

Description

SeleniumTestCase always assumes that the selenium server is running on the default port, even 'though it can be modified via a system property ("selenium.port").

When that system property is set (either intentionally or accidentally), then the selenium server is started correctly, but the command processor fails to connect to it.

The solution is simple. Replace this statement:

CommandProcessor httpCommandProcessor = new HttpCommandProcessor("localhost",
RemoteControlConfiguration.DEFAULT_PORT, browserStartCommand, baseURL);

with this:

CommandProcessor httpCommandProcessor = new HttpCommandProcessor("localhost",
seleniumServer.getPort(), browserStartCommand, baseURL);