You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Joachim Sauer (JIRA)" <ji...@apache.org> on 2013/09/12 08:13:51 UTC

[jira] [Created] (TAP5-2180) SeleniumTestCase assumes that selenium runs on the default port

Joachim Sauer created TAP5-2180:
-----------------------------------

             Summary: SeleniumTestCase assumes that selenium runs on the default port
                 Key: TAP5-2180
                 URL: https://issues.apache.org/jira/browse/TAP5-2180
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-test
    Affects Versions: 5.3.7
            Reporter: Joachim Sauer
            Priority: Minor


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);


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira