| Class | Selenium::Rake::RemoteControlStartTask |
| In: |
lib/selenium/rake/remote_control_start_task.rb
|
| Parent: | Object |
Rake tasks to start a Remote Control server.
require ‘selenium/rake/tasks‘
Selenium::Rake::RemoteControlStartTask.new do |rc|
rc.port = 4444 rc.timeout_in_seconds = 3 * 60 rc.background = true rc.wait_until_up_and_running = true rc.jar_file = "/path/to/where/selenium-rc-standalone-jar-is-installed" rc.additional_args << "-singleWindow"
end
If you do not explicitly specify the path to selenium remote control jar it will be "auto-discovered" in `vendor` directory using the following path : `vendor/selenium-remote-control/selenium-server*-standalone.jar`
To leverage the latest selenium-client capabilities, you may need to download a recent nightly build of a standalone packaging of Selenium Remote Control. You will find the nightly build at nexus.openqa.org/content/repositories/snapshots/org/seleniumhq/selenium/server/selenium-server/
| JAR_FILE_PATTERN | = | "vendor/selenium-remote-control/selenium-server-*.jar" |
| additional_args | [RW] | |
| background | [RW] | |
| host | [RW] | |
| jar_file | [R] | |
| log_to | [RW] | |
| port | [RW] | |
| timeout_in_seconds | [RW] | |
| wait_until_up_and_running | [RW] |