Instruct selenider to use RSelenium instead of selenium. Passed into
selenium_options()
. This is not recommended, since RSelenium does not
support the latest version of Selenium, and wdman (the server manager that
RSelenium) uses, is not compatible with the latest version of Chrome.
Usage
wdman_server_options(
version = "latest",
driver_version = "latest",
port = 4444L,
check = TRUE,
verbose = FALSE,
retcommand = FALSE,
...
)
rselenium_client_options(
port = 4444L,
host = "localhost",
path = "/wd/hub",
version = "",
platform = "ANY",
javascript = TRUE,
native_events = TRUE,
extra_capabilities = list()
)
Arguments
- version
The version of Selenium server to use.
- driver_version
The version of the browser-specific driver to use.
- port
The port to run selenium client/server on.
- check, verbose, retcommand, ...
Passed into
wdman::selenium()
.- host
The host to connect to the selenium server over.
- path, platform, javascript, native_events, extra_capabilities
Passed into
RSelenium::remoteDriver()
.
Value
An options object that can be passed into selenium_options()
.
Details
In selenium_options()
, you can supply options to configure a server and
client run by RSelenium instead of selenium.
Instead of selenium_server_options()
, you can use wdman_server_options()
to allow wdman
to run the Selenium server using wdman::selenium()
.
Instead of using selenium_client_options()
, you can use
rselenium_client_options()
to control the creation of an
RSelenium::remoteDriver()
object instead.
Note that the driver
option of selenider_session()
also accepts these
objects in place of their selenium equivalents.