You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/11/04 23:45:18 UTC
[jira] [Commented] (TAP5-2180) SeleniumTestCase assumes that
Selenium Server runs on the default port
[ https://issues.apache.org/jira/browse/TAP5-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813374#comment-13813374 ]
ASF subversion and git services commented on TAP5-2180:
-------------------------------------------------------
Commit c4ecab24fac1f88b971e6b6e0d8319a14c828c39 in branch refs/heads/master from [~hlship]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=c4ecab2 ]
TAP5-2180: SeleniumTestCase assumes that Selenium Server 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)