tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAP5-2180) SeleniumTestCase assumes that Selenium Server runs on the default port
Date Mon, 04 Nov 2013 22:45:17 GMT

     [ https://issues.apache.org/jira/browse/TAP5-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship updated TAP5-2180:
---------------------------------------

    Summary: SeleniumTestCase assumes that Selenium Server runs on the default port  (was:
SeleniumTestCase assumes that selenium runs on the default port)

> SeleniumTestCase assumes that Selenium Server 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
>             Fix For: 5.4
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message