s/1/2

Author: ddavison

NodeChromeDebug/README.md

@@ -38,7 +38,7 @@ If you are running Boot2Docker on Mac then you already have a [VNC client](http:
 When you are prompted for the password it is __secret__. If you wish to change this then you should either change it in the `/NodeBase/Dockerfile` and build the images yourself, or you can define a docker image that derives from the posted ones which reconfigures it:
 
 ``` dockerfile
-FROM selenium/node-chrome-debug:3.1.0-actinium
+FROM selenium/node-chrome-debug:3.2.0-actinium
 
 RUN x11vnc -storepasswd <your-password-here> /home/seluser/.vnc/passwd
 ```

NodeDebug/README.template.md

@@ -38,7 +38,7 @@ If you are running Boot2Docker on Mac then you already have a [VNC client](http:
 When you are prompted for the password it is __secret__. If you wish to change this then you should either change it in the `/NodeBase/Dockerfile` and build the images yourself, or you can define a docker image that derives from the posted ones which reconfigures it:
 
 ``` dockerfile
-FROM selenium/##BASE##-debug:3.1.0-actinium
+FROM selenium/##BASE##-debug:3.2.0-actinium
 
 RUN x11vnc -storepasswd <your-password-here> /home/seluser/.vnc/passwd
 ```

NodeFirefoxDebug/Dockerfile.txt

@@ -1,4 +1,4 @@
-FROM selenium/node-firefox:3.1.0-actinium
+FROM selenium/node-firefox:3.2.0-actinium
 MAINTAINER Selenium <selenium-developers@googlegroups.com>
 
 USER root

NodeFirefoxDebug/README.md

@@ -38,7 +38,7 @@ If you are running Boot2Docker on Mac then you already have a [VNC client](http:
 When you are prompted for the password it is __secret__. If you wish to change this then you should either change it in the `/NodeBase/Dockerfile` and build the images yourself, or you can define a docker image that derives from the posted ones which reconfigures it:
 
 ``` dockerfile
-FROM selenium/node-firefox-debug:3.1.0-actinium
+FROM selenium/node-firefox-debug:3.2.0-actinium
 
 RUN x11vnc -storepasswd <your-password-here> /home/seluser/.vnc/passwd
 ```

README.md

@@ -26,7 +26,7 @@ Images included:
 When executing docker run for an image with chrome browser please add volume mount `-v /dev/shm:/dev/shm` to use the host's shared memory.
 
 ``` bash
-$ docker run -d -p 4444:4444 -v /dev/shm:/dev/shm selenium/standalone-chrome:3.1.0-actinium
+$ docker run -d -p 4444:4444 -v /dev/shm:/dev/shm selenium/standalone-chrome:3.2.0-actinium
 ```
 
 This is a workaround to node-chrome crash in docker container issue: https://code.google.com/p/chromium/issues/detail?id=519952
@@ -35,9 +35,9 @@ This is a workaround to node-chrome crash in docker container issue: https://cod
 ### Standalone Chrome and Firefox
 
 ``` bash
-$ docker run -d -p 4444:4444 selenium/standalone-chrome:3.1.0-actinium
+$ docker run -d -p 4444:4444 selenium/standalone-chrome:3.2.0-actinium
 # OR
-$ docker run -d -p 4444:4444 selenium/standalone-firefox:3.1.0-actinium
+$ docker run -d -p 4444:4444 selenium/standalone-firefox:3.2.0-actinium
 ```
 
 _Note: Only one standalone image can run on port_ `4444` _at a time._
@@ -47,9 +47,9 @@ To inspect visually what the browser is doing use the `standalone-chrome-debug`
 ### Selenium Grid Hub and Nodes
 
 ``` bash
-$ docker run -d -p 4444:4444 --name selenium-hub selenium/hub:3.1.0-actinium
-$ docker run -d --link selenium-hub:hub selenium/node-chrome:3.1.0-actinium
-$ docker run -d --link selenium-hub:hub selenium/node-firefox:3.1.0-actinium
+$ docker run -d -p 4444:4444 --name selenium-hub selenium/hub:3.2.0-actinium
+$ docker run -d --link selenium-hub:hub selenium/node-chrome:3.2.0-actinium
+$ docker run -d --link selenium-hub:hub selenium/node-firefox:3.2.0-actinium
 ```
 
 ## Configuring the containers
@@ -59,15 +59,15 @@ $ docker run -d --link selenium-hub:hub selenium/node-firefox:3.1.0-actinium
 You can pass `JAVA_OPTS` environment variable to java process.
 
 ``` bash
-$ docker run -d -p 4444:4444 -e JAVA_OPTS=-Xmx512m --name selenium-hub selenium/hub:3.1.0-actinium
+$ docker run -d -p 4444:4444 -e JAVA_OPTS=-Xmx512m --name selenium-hub selenium/hub:3.2.0-actinium
 ```
 
 ### SE_OPTS Selenium Configuration Options
 
 You can pass `SE_OPTS` variable with additional commandline parameters for starting a hub or a node.
 
 ``` bash
-$ docker run -d -p 4444:4444 -e SE_OPTS=-debug --name selenium-hub selenium/hub:3.1.0-actinium
+$ docker run -d -p 4444:4444 -e SE_OPTS=-debug --name selenium-hub selenium/hub:3.2.0-actinium
 ```
 
 ### PHANTOMJS_OPTS PhantomJS Configuration Options
@@ -99,10 +99,10 @@ _Note: Omitting_ `VERSION=local` _will build the images with the current version
 ##### Example: Spawn a container for testing in Chrome:
 
 ``` bash
-$ docker run -d --name selenium-hub -p 4444:4444 selenium/hub:3.1.0-actinium
+$ docker run -d --name selenium-hub -p 4444:4444 selenium/hub:3.2.0-actinium
 $ CH=$(docker run --rm --name=ch \
     --link selenium-hub:hub -v /e2e/uploads:/e2e/uploads \
-    selenium/node-chrome:3.1.0-actinium)
+    selenium/node-chrome:3.2.0-actinium)
 ```
 
 _Note:_ `-v /e2e/uploads:/e2e/uploads` _is optional in case you are testing browser uploads on your web app you will probably need to share a directory for this._
@@ -112,10 +112,10 @@ _Note:_ `-v /e2e/uploads:/e2e/uploads` _is optional in case you are testing brow
 This command line is the same as for Chrome. Remember that the Selenium running container is able to launch either Chrome or Firefox, the idea around having 2 separate containers, one for each browser is for convenience plus avoiding certain `:focus` issues your web app may encounter during end-to-end test automation.
 
 ``` bash
-$ docker run -d --name selenium-hub -p 4444:4444 selenium/hub:3.1.0-actinium
+$ docker run -d --name selenium-hub -p 4444:4444 selenium/hub:3.2.0-actinium
 $ FF=$(docker run --rm --name=fx \
     --link selenium-hub:hub -v /e2e/uploads:/e2e/uploads \
-    selenium/node-firefox:3.1.0-actinium)
+    selenium/node-firefox:3.2.0-actinium)
 ```
 
 _Note: Since a Docker container is not meant to preserve state and spawning a new one takes less than 3 seconds you will likely want to remove containers after each end-to-end test with_ `--rm` _command. You need to think of your Docker containers as single processes, not as running virtual machines, in case you are familiar with [Vagrant](https://www.vagrantup.com/)._
@@ -124,28 +124,28 @@ _Note: Since a Docker container is not meant to preserve state and spawning a ne
 
 In the event you wish to visually see what the browser is doing you will want to run the `debug` variant of node or standalone images. A VNC server will run on port 5900. You are free to map that to any free external port that you wish.  Example: <port4VNC>: 5900) you will only be able to run 1 node per port so if you wish to include a second node, or more, you will have to use different ports, the 5900 as the internal port will have to remain the same though as thats the VNC service on the node. The second example below shows how to run multiple nodes and with different VNC ports open:
 ``` bash
-$ docker run -d -P -p <port4VNC>:5900 --link selenium-hub:hub selenium/node-chrome-debug:3.1.0-actinium
-$ docker run -d -P -p <port4VNC>:5900 --link selenium-hub:hub selenium/node-firefox-debug:3.1.0-actinium
+$ docker run -d -P -p <port4VNC>:5900 --link selenium-hub:hub selenium/node-chrome-debug:3.2.0-actinium
+$ docker run -d -P -p <port4VNC>:5900 --link selenium-hub:hub selenium/node-firefox-debug:3.2.0-actinium
 ```
 e.g.:
 ``` bash
-$ docker run -d -P -p 5900:5900 --link selenium-hub:hub selenium/node-chrome-debug:3.1.0-actinium
-$ docker run -d -P -p 5901:5900 --link selenium-hub:hub selenium/node-firefox-debug:3.1.0-actinium
+$ docker run -d -P -p 5900:5900 --link selenium-hub:hub selenium/node-chrome-debug:3.2.0-actinium
+$ docker run -d -P -p 5901:5900 --link selenium-hub:hub selenium/node-firefox-debug:3.2.0-actinium
 ```
 
 to connect to the Chrome node on 5900 and the Firefox node on 5901 (assuming those node are free, and reachable).
 
 And for standalone:
 ``` bash
-$ docker run -d -p 4444:4444 -p <port4VNC>:5900 selenium/standalone-chrome-debug:3.1.0-actinium
+$ docker run -d -p 4444:4444 -p <port4VNC>:5900 selenium/standalone-chrome-debug:3.2.0-actinium
 # OR
-$ docker run -d -p 4444:4444 -p <port4VNC>:5900 selenium/standalone-firefox-debug:3.1.0-actinium
+$ docker run -d -p 4444:4444 -p <port4VNC>:5900 selenium/standalone-firefox-debug:3.2.0-actinium
 ```
 or
 ``` bash
-$ docker run -d -p 4444:4444 -p 5900:5900 selenium/standalone-chrome-debug:3.1.0-actinium
+$ docker run -d -p 4444:4444 -p 5900:5900 selenium/standalone-chrome-debug:3.2.0-actinium
 # OR
-$ docker run -d -p 4444:4444 -p 5901:5900 selenium/standalone-firefox-debug:3.1.0-actinium
+$ docker run -d -p 4444:4444 -p 5901:5900 selenium/standalone-firefox-debug:3.2.0-actinium
 ```
 
 You can acquire the port that the VNC server is exposed to by running:
@@ -164,8 +164,8 @@ If you are running [Boot2Docker](https://docs.docker.com/installation/mac/) on O
 
 When you are prompted for the password it is `secret`. If you wish to change this then you should either change it in the `/NodeBase/Dockerfile` and build the images yourself, or you can define a Docker image that derives from the posted ones which reconfigures it:
 ``` dockerfile
-#FROM selenium/node-chrome-debug:3.1.0-actinium
-#FROM selenium/node-firefox-debug:3.1.0-actinium
+#FROM selenium/node-chrome-debug:3.2.0-actinium
+#FROM selenium/node-firefox-debug:3.2.0-actinium
 #Choose the FROM statement that works for you.
 
 RUN x11vnc -storepasswd <your-password-here> /home/seluser/.vnc/passwd

sa-test.sh

@@ -13,7 +13,7 @@ function test_standalone {
   BROWSER=$1
   echo Starting Selenium standalone-$BROWSER$DEBUG container
 
-  SA=$(docker run -d selenium/standalone-$BROWSER$DEBUG:3.1.0-actinium)
+  SA=$(docker run -d selenium/standalone-$BROWSER$DEBUG:3.2.0-actinium)
   SA_NAME=$(docker inspect -f '{{ .Name  }}' $SA | sed s:/::)
   TEST_CMD="node smoke-$BROWSER.js"
 

test.sh

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 DEBUG=''
-VERSION=${VERSION:-3.1.0-actinium}
+VERSION=${VERSION:-3.2.0-actinium}
 
 if [ -n "$1" ] && [ $1 == 'debug' ]; then
   DEBUG='-debug'
@@ -24,7 +24,7 @@ echo Building test container image
 docker build -t selenium/test:local ./Test
 
 echo 'Starting Selenium Hub Container...'
-HUB=$(docker run -d selenium/hub:3.1.0-actinium)
+HUB=$(docker run -d selenium/hub:3.2.0-actinium)
 HUB_NAME=$(docker inspect -f '{{ .Name  }}' $HUB | sed s:/::)
 echo 'Waiting for Hub to come online...'
 docker logs -f $HUB &