From 31fbee7884b8a2b88af5bea64897b39e2afbfae7 Mon Sep 17 00:00:00 2001 From: "J. Kim" Date: Mon, 17 Sep 2018 11:41:54 -0700 Subject: [PATCH] Update pkgdown --- docs/articles/basics.html | 2 +- docs/articles/docker.html | 18 +++++++++--------- docs/articles/saucelabs.html | 14 +++++++------- 3 files changed, 17 insertions(+), 17 deletions(-) diff --git a/docs/articles/basics.html b/docs/articles/basics.html index 0a9b8fb..9b53e48 100644 --- a/docs/articles/basics.html +++ b/docs/articles/basics.html @@ -511,7 +511,7 @@

RProject front page
-

+

To access the content, we have to switch to a frame using the switchToFrame method of the remoteDriver class.

webElems <- remDr$findElements(using = "tag name", "frame")
 # webElems <- remDr$findElements(value = "//frame") # using xpath
diff --git a/docs/articles/docker.html b/docs/articles/docker.html
index 0f8564a..260da93 100644
--- a/docs/articles/docker.html
+++ b/docs/articles/docker.html
@@ -117,7 +117,7 @@ 

 
Depending on your version of windows there are currently two ways of running docker. Details are given at Docker. For the version of windows Being used in this vignette (win 10 home) the older Docker toolbox is what we are going to use to run containers.

 
Download the .exe for Docker toolbox and begin the install. Follow the instructions on the toolbox install windows page.

 
Clicking on the Docker Quickstart terminal link should eventually give you a terminal that resembles the following:

-

+
@@ -146,7 +146,7 @@

You can check that the Docker is working by running a test container:

For now run as sudo

sudo docker run hello-world
-

+

@@ -159,12 +159,12 @@

Using Selenium Docker Images

The official docker repository can be viewed here at Docker Hub.

-

+

What’s in an Image?

Lets examine the selenium/node-firefox image. The first thing to note is the Tags.

-

+

Clicking this gives us the various tagged versions of this image. Clicking Dockerfile allows us to view the source behind the image:

FROM selenium/node-base:2.53.0 
 MAINTAINER Selenium <selenium-developers@googlegroups.com> 
@@ -186,7 +186,7 @@ 

 
We then issue the following command:

 
docker pull selenium/standalone-firefox:2.53.0

 
Notice we appended a tag version so we are asking for the 2.53.0 version of this image.

-

+

@@ -207,7 +207,7 @@ 

docker run -d -p 4445:4444 selenium/standalone-firefox:2.53.0

For illustration here we are mapping the container port 4444 to the host port 4445 so when we want to refer to our server on the host machine we will use 4445 as the port.

We also run the ps command after running to show our current running containers.

-

+

So we can see an instance of standalone-firefox:2.53.0 is running. It has id=ac61567a8f06 and is named peaceful_aryabhata.

@@ -217,7 +217,7 @@

Again run as sudo if necessary:

sudo docker run -d -p 4445:4444 selenium/standalone-firefox:2.53.0
 sudo docker ps
-

+

The Ubuntu container has id=5475923fc4dc and is named peaceful_payne.

A tip if you dont want to strain your eyes is to use the --format argument:

sudo docker ps --format 'table {{.Names}}\t{{.Image}}\t{{.ID}}'
@@ -426,7 +426,7 @@

remDr$getTitle() remDr$screenshot(display = TRUE)

Now we open TightVNC and use the VM ip with appropriate port for VNC:

-

+

You will be asked for a password which is secret. This can be seen by reading the images dockerfile:

RUN apt-get update -qqy \
   && apt-get -qqy install \
@@ -495,7 +495,7 @@ 

 
## [[1]]
 ## [1] "Google"

 
Now open Vinagre and input the correct ip/port (127.0.0.1:5901 in this case):

-

+

 
Again it will ask for a password which as before is secret.

 
You should now be able to interact with the containers browser. Again navigate to another website and observe the containers browser:

 
remDr$navigate("http://www.bbc.com")
diff --git a/docs/articles/saucelabs.html b/docs/articles/saucelabs.html
index 44e40f0..4f940d4 100644
--- a/docs/articles/saucelabs.html
+++ b/docs/articles/saucelabs.html
@@ -332,7 +332,7 @@ 

 

 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.

 

 

@@ -376,7 +376,7 @@ 

 

 Android SDK on win 8.1
 

-

+

 
From the tools make sure all are installed. From the latest android release Android 4.4.2 (API 19) in this case make sure all are installed. From the Extras folder, select the checkbox for the Android Support Library and make sure it is installed. You will also want to install the Intel Hardware Accelerated Execution Manager. Instructions on how to do so are here. Basically checking the box Intel x86 Emulator Accelerator (HAXM) and “installing” will download it to %ANDROID_HOME%/extras/intel. In this folder is an exe IntelHaxm.exe which should be ran to finish the install.

 

 

@@ -386,17 +386,17 @@ 

 

 Android AVD on win 8.1
 

-

+

 
You can see I have created an avd already named “my_avd”. You will need to create one by clicking new. The details for the “my_avd” are shown here

 

 Android AVD my_avd on win 8.1
 

-

+

 
Click ok and an avd should have been created. You can start it using the panel. Click the newly created avd then click start. It will take a few moments but a panel containing a virtual phone will hopefully boot up and eventually get to the phone screen.

 

 Android AVD my_avd on win 8.1
 

-

+

 
If you have got to this point it is most likely you will now be able to drive this phone with selendroid. Take a few moments to play with your virtual android phone ;).

 

 

@@ -416,7 +416,7 @@ 

 

 Android with RSelenium on win 8.1
 

-

+
@@ -525,7 +525,7 @@

Sauce Labs results for simple test script
-

+