You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: NodeChromeDebug/README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ If you are running Boot2Docker on Mac then you already have a [VNC client](http:
38
38
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:
39
39
40
40
```dockerfile
41
-
FROM selenium/node-chrome-debug:3.3.1-arsenic
41
+
FROM selenium/node-chrome-debug:3.3.1-bohrium
42
42
43
43
RUN x11vnc -storepasswd <your-password-here> /home/seluser/.vnc/passwd
Copy file name to clipboardExpand all lines: NodeDebug/README.template.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ If you are running Boot2Docker on Mac then you already have a [VNC client](http:
38
38
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:
39
39
40
40
```dockerfile
41
-
FROM selenium/##BASE##-debug:3.3.1-arsenic
41
+
FROM selenium/##BASE##-debug:3.3.1-bohrium
42
42
43
43
RUN x11vnc -storepasswd <your-password-here> /home/seluser/.vnc/passwd
Copy file name to clipboardExpand all lines: NodeFirefoxDebug/README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ If you are running Boot2Docker on Mac then you already have a [VNC client](http:
38
38
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:
39
39
40
40
```dockerfile
41
-
FROM selenium/node-firefox-debug:3.3.1-arsenic
41
+
FROM selenium/node-firefox-debug:3.3.1-bohrium
42
42
43
43
RUN x11vnc -storepasswd <your-password-here> /home/seluser/.vnc/passwd
_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._
@@ -118,10 +118,10 @@ _Note:_ `-v /e2e/uploads:/e2e/uploads` _is optional in case you are testing brow
118
118
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.
119
119
120
120
```bash
121
-
$ docker run -d --name selenium-hub -p 4444:4444 selenium/hub:3.3.1-arsenic
121
+
$ docker run -d --name selenium-hub -p 4444:4444 selenium/hub:3.3.1-bohrium
_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/)._
@@ -130,28 +130,28 @@ _Note: Since a Docker container is not meant to preserve state and spawning a ne
130
130
131
131
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:
132
132
```bash
133
-
$ docker run -d -P -p <port4VNC>:5900 --link selenium-hub:hub selenium/node-chrome-debug:3.3.1-arsenic
134
-
$ docker run -d -P -p <port4VNC>:5900 --link selenium-hub:hub selenium/node-firefox-debug:3.3.1-arsenic
133
+
$ docker run -d -P -p <port4VNC>:5900 --link selenium-hub:hub selenium/node-chrome-debug:3.3.1-bohrium
134
+
$ docker run -d -P -p <port4VNC>:5900 --link selenium-hub:hub selenium/node-firefox-debug:3.3.1-bohrium
135
135
```
136
136
e.g.:
137
137
```bash
138
-
$ docker run -d -P -p 5900:5900 --link selenium-hub:hub selenium/node-chrome-debug:3.3.1-arsenic
139
-
$ docker run -d -P -p 5901:5900 --link selenium-hub:hub selenium/node-firefox-debug:3.3.1-arsenic
138
+
$ docker run -d -P -p 5900:5900 --link selenium-hub:hub selenium/node-chrome-debug:3.3.1-bohrium
139
+
$ docker run -d -P -p 5901:5900 --link selenium-hub:hub selenium/node-firefox-debug:3.3.1-bohrium
140
140
```
141
141
142
142
to connect to the Chrome node on 5900 and the Firefox node on 5901 (assuming those node are free, and reachable).
143
143
144
144
And for standalone:
145
145
```bash
146
-
$ docker run -d -p 4444:4444 -p <port4VNC>:5900 selenium/standalone-chrome-debug:3.3.1-arsenic
146
+
$ docker run -d -p 4444:4444 -p <port4VNC>:5900 selenium/standalone-chrome-debug:3.3.1-bohrium
147
147
# OR
148
-
$ docker run -d -p 4444:4444 -p <port4VNC>:5900 selenium/standalone-firefox-debug:3.3.1-arsenic
148
+
$ docker run -d -p 4444:4444 -p <port4VNC>:5900 selenium/standalone-firefox-debug:3.3.1-bohrium
149
149
```
150
150
or
151
151
```bash
152
-
$ docker run -d -p 4444:4444 -p 5900:5900 selenium/standalone-chrome-debug:3.3.1-arsenic
152
+
$ docker run -d -p 4444:4444 -p 5900:5900 selenium/standalone-chrome-debug:3.3.1-bohrium
153
153
# OR
154
-
$ docker run -d -p 4444:4444 -p 5901:5900 selenium/standalone-firefox-debug:3.3.1-arsenic
154
+
$ docker run -d -p 4444:4444 -p 5901:5900 selenium/standalone-firefox-debug:3.3.1-bohrium
155
155
```
156
156
157
157
You can acquire the port that the VNC server is exposed to by running:
@@ -170,8 +170,8 @@ If you are running [Boot2Docker](https://docs.docker.com/installation/mac/) on O
170
170
171
171
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:
172
172
```dockerfile
173
-
#FROM selenium/node-chrome-debug:3.3.1-arsenic
174
-
#FROM selenium/node-firefox-debug:3.3.1-arsenic
173
+
#FROM selenium/node-chrome-debug:3.3.1-bohrium
174
+
#FROM selenium/node-firefox-debug:3.3.1-bohrium
175
175
#Choose the FROM statement that works for you.
176
176
177
177
RUN x11vnc -storepasswd <your-password-here> /home/seluser/.vnc/passwd
0 commit comments