Comment #14 on issue 99 by javierch...@gmail.com: Support Firefox 3.6 by updating the embedded Selenium Server to 1.0.3 version
http://code.google.com/p/robotframework-seleniumlibrary/issues/detail?id=99

I have been following these tutorials on RF-seleniumLibrary automation:
http://www.wallix.org/2011/07/26/how-to-use-robotframework-with-the-selenium-library/
http://www.wallix.org/2011/09/06/how-to-use-robotframework-part-2/

When using the following parameters in file common.txt:

*** Settings ***
Documentation  This resource file contains common and global variables
Library   SeleniumLibrary  25  localhost

*** Variables ***
# Choose Firefox Chrome Browser :
# Here you can change your web browser.
${browser}   googlechrome
${sel_speed}  0


Then run the test cases, I got following error:

Could not connect to Selenium Server in 120 seconds. Please make sure Selenium Server is running.


But, if just I use these parameters for library:
Library   SeleniumLibrary  25  localhost

... the test cases run as expected.

But also, if I use the following parameters:
Library SeleniumLibrary timeout=25 server_host=localhost server_port=5556

The problem with the selenium server persists.

Of course that I have the selenium server up and running in all cases.

I'm using:
RobotFramework 2.7.5
SeleniumLibrary 2.9.1
Java jre 6_23

Maybe you can give me any hint on why the port parameter cannot be correctly recognized?

I-m a newbie with these tools, so probably this is a very basic error that I cannot see. Thanks,

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

--- You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to