If you don't specify anything, we'll default to the driver's default port. Optional: specify the port that we should bind to. If you don't specify anything, we'll search for geckodriver in your $PATH.įor Firefox 47 and older, this attribute does not apply, because the older FF browsers do not use the separate driver binary startup. To specify the path to your Firefox browser binary, see the "firefox_binary" attr.įor Firefox 48 and greater, this is the path to your geckodriver executable. Optional: specify the path to the geckodriver binary - this is NOT the path to the Firefox browser. If you're curious whether your Selenium::Firefox instance is using a separate Firefox binary, or through the selenium server, you can check the value of the binary_mode attr after instantiation. If you specify a remote server address, or a port, our assumption is that you are doing standard S::R::D behavior and we will not attempt any binary startup. If the Firefox application is not found in the expected places, we'll fall back to the default Selenium::Remote::Driver behavior of assuming defaults of 127.0.0.1:4444 after waiting a few seconds. We'll try to start the binary, connect to it, and shut it down at the end of the test. Unlike starting up an instance of S::R::D, do not pass the remote_server_addr and port arguments, and we will search for the Firefox executable in your $PATH. This class allows you to use the FirefoxDriver without needing the JRE or a selenium server running. You can ignore this if you're using v1.0+ of this module to start FF48.
$driver = Selenium::Firefox->new( marionette_enabled => 0 ) īreaking Changes: There are breaking changes in v1.0+ of this module if you're using it to start FF47 please see "BREAKING CHANGES". # For Firefox 47 and older, disable marionette: $driver = Selenium::Firefox->new( marionette_enabled => 1 ) Version 1.48 SYNOPSIS # These two are the same, and will only work with Firefox 48+ Import .Selenium::Firefox - Use FirefoxDriver without a Selenium server VERSION
0 kommentar(er)
