rselenium download phantomjs driver rsDriver : Start a selenium server and browser. what version of Chrome driver to run. Default = "latest" which runs the most recent version. To see other version currently sourced run binman::list_versions("chromedriver"), A value of NULL excludes adding the chrome browser to Selenium Server. what version of Gecko driver to run. Default = "latest" which runs the most recent version. To see other version currently sourced run binman::list_versions("geckodriver"), A value of NULL excludes adding the firefox browser to Selenium Server. what version of IEDriverServer to run. Default = "latest" which runs the most recent version. To see other version currently sourced run binman::list_versions("iedriverserver"), A value of NULL excludes adding the internet explorer browser to Selenium Server. NOTE this functionality is Windows OS only. what version of PhantomJS to run. Default = "2.1.1" which runs the most recent stable version. To see other version currently sourced run binman::list_versions("phantomjs"), A value of NULL excludes adding the PhantomJS headless browser to Selenium Server. If TRUE, include status messages (if any) If TRUE check the versions of selenium available and the versions of associated drivers (chromever, geckover, phantomver, iedrver). If new versions are available they will be downloaded. Additional arguments to pass to remoteDriver. Details. This function is a wrapper around selenium . It provides a "shim" for the current issue running firefox on Windows. For a more detailed set of functions for running binaries relating to the Selenium/webdriver project see the wdman package. Both the client and server are closed using a registered finalizer. Value. A list containing a server and a client. The server is the object returned by selenium and the client is an object of class remoteDriver. Driving OS/Browsers Local and Remote. The goal of this vignette is to give a basic overview of how one might approach using RSelenium with combinations of operating systems (OS) and browsers both locally and remotely. RSelenium with Local Fully-fledged Browsers. Firefox. The default browser for RSelenium is firefox. When a remoteDriver class is instantiated using default options for example remdr <- remoteDriver() then the browser listed is firefox. Other browsers can be driven using RSelenium . We shall split these browsers into three groups. Full-fledged browsers, headless browsers and mobile browsers. The standalone selenium jar has the ability to drive other full-fledged browsers such as chrome, internet explorer, safari and opera. First we shall look at how to drive chrome using RSelenium. Chrome. Firstly we note that chrome in this instance can be considered as having three parts. There is the browser itself (“chrome”), the language bindings provided by the Selenium project (“the driver”) and an executable downloaded from the Chromium project which acts as a bridge between “chrome” and the “driver”. This executable is called “chromedriver”. We need to have a “chromedriver” running. First we need to locate one. The download directory for chromedriver is currently located at http://chromedriver.storage.googleapis.com/index.html. In this example we shall look at running chrome on a windows platform so we will download the windows chromedriver. The most uptodate version of chromedriver at the time of writing was 2.9. In the notes this supports chrome v31-34. We are running chrome 33 so this is fine. We download the appropriate file for windows and extract the .exe to our Documents folder. The .exe can be placed where the user pleases but it must be in the system path. In this case we placed in the Documents folder namely C:. This directory was added to the system path. We assume that a selenium server is also running if not one can be started using RSelenium::startServer() . Now we are done. A chrome browser can be controlled as follows: Internet Explorer. Similarly to the chrome browser you do not need to run an installer before using the InternetExplorerDriver, though some configuration is required. The standalone server executable must be downloaded from the Downloads page and placed in your PATH. Again we need to download this executable and place it in our path. At the time of writing the internet explorer .exe is included with the main standalone server here. The current release is 2.40. The system I am running is 64 bit so we download the 64bit version. For simplicity we again place this in our Documents directory namely C:. This directory is already in the system path from running the chrome example. If you want to place the internet explorer .exe in another folder add this folder to your system path. To control internet explorer as a browser is now as simple as: Safari. Currently Apple have discontinued developement of safari for windows. The latest version for windows was 5.1.7 available here. Starting with Selenium 2.30.0, the SafariDriver comes bundled with the Selenium server so nothing other then having safari installed should be required. For the purposes of this vignette I downloaded and installed safari 5.1.7 on a windows 8.1 system. Once installed controlling safari was as easy as: Opera. Opera is currently not supported for versions newer then 12. http://code.google.com/p/selenium/wiki/OperaDriver gives details on the current status. For the purposes of this vignette I downloaded and installed the 64 bit version of 12.16 located here. I had some issues getting this to run YMMV however. The first issue was getting the following error message. So not surprising win 8.1 was first unveiled and released as a public beta in June 2013 and on July 4, 2013, Opera 12.16 was released being the last current version of opera supported by selenium. OperaLauncherRunner.java located here does not currently cater for the WIN8 enum returned by Platform.getCurrent(). The solution is to start the selenium server with additional parameters passed to java (RSelenium::startServer doesn’t pass arguments to java atm) This is actually using java -D which is used to set a system property. The system property we set is os.name . This is nothing to do with selenium- server and the appearance of Dos is a coincidence not related to DOS. Now we get a new issue. So in this case we refer to the operadriver wiki. It states that the OperaDriver server expects you to have Opera or Opera Next installed in the default location for each system which for windows is %PROGRAMFILES%.exe or more precisely C:Files.exe. As I have installed the 64bit version I need to tell opera driver where to look. A few small issues. I suspect if you were running win 7 or lower and the 32 bit version of opera 12.16 it would probably run out of the box. RSelenium with Local Headless Browsers. Next we shall look at running what is known as headless browsers. Usually a browser can do three things. For given url, download the html page (or any other content apart from html) Render the content into dom, eg executing javascript inside the script tag. and the executed result will be reflected on the browsers dom. Render the dom into visualised content. A headless browser handles items 1 and 2 but doesn’t carryout 3. This means it doesn’t display anything. All pages etc. are in memory rather then displayed to the user. The result of this is that headless browsers should perform faster then their full-fledged competitors which could be welcome news to speed up testing. phantomjs. The first headless browser we shall look at is phantomjs . Firstly download the relevant zip file for your OS from here. We are using windows so we downloaded phantomjs-2.1.1-windows.zip. It is sufficient to place the location of the directory containing phantomjs.exe in your path. In this case we probably could have just extracted phantomjs.exe to the Documents folder where chromedriver etc current reside. However I extracted it to the desktop keeping the contents of the zip. The reasoning behind this was that phantomjs is driven by selenium using ghostdriver. At some point the version of ghostdriver phantomjs uses will be upgraded and will accept calls from an unexposed method phantomExecute of the RSelenium remoteDriver class. There are interesting scripts contained in the phantomjs /example directory like netsniff.js which captures network traffic in HAR format. When the phantomExecute method is exposed these scripts will be useful. So I added the location of the .exe to my path namely the directory C:-1.9.7-windows. Once your operating system can find phantomjs.exe or the equivalent driving a phantomjs browser is as easy as: We can take a screenshot even thou the browser is headless: RSelenium on win 8.1 driving phantomjs. PhantomJS is excellent. It has only recently as of version 1.8 had Ghost Driver integration and hopefully its importance will increase further. HtmlUnit. The original headless browser for selenium was htmlunit . RSelenium with Local Mobile Browsers. Configuring your local machine to use mobile browsers can be slightly tricky. If you are having difficulty setting up on your particular OS you may want to skip this section. Android. The first mobile browser we will look at driving is Android. The selenium project had android drivers in the selenium project. The current state of these drivers is listed here. As can be noted driving android using the selenium server has been deprecated in favour of the selendroid project. Once selendroid has been setup this means that rather than running the selenium standalone jar as a server we will be running an equivalent selendroid jar to drive our browser on our real or emulated android phone.