Integration tests are an integral part of any modern web application, and regardless of which front-end or server side framework you choose, you'll likely be running Selenium tests. While Selenium tests are easy to write and execute on your local workstation, Works On My Machine™ won't get you past your CI system. Now you're stuck with two bad options, use a SaaS provider and live with slow builds or running your own Selenium Grid and managing a multitude of machines and browser versions. Rock, meet hard place, right? It doesn't have to be that way! In this talk you'll see how easy it is to setup a Selenium Grid with Docker, how easy it is to maintain, and how to extend and grow your Selenium grid to satisfy your team's needs. It's not all roses and sunshine, so you'll see some common issues presented and how to avoid them. Finally, a Selenium Grid you'll want to manage!

1. Browser Testing with
Docker
Craig Huber
Manager Development Operations,
Capital One

2. Browser Testing with
Docker
Qirui Yang
Sr. Test Engineer,
Capital One

3. We’ll talk about
1. Options for browser testing
2. Where Docker fits in
3. What has worked for us
Agenda
You’ll learn
1. How to set it up
2. What to do (and not)

4. UI testing is time consuming
to run
Developers want fast
feedback
Business wants cross
browser testing
Current State

5. Everything is fine until you realize:
• VPN connection: slow and complicated
• Wait time: VM spin up and session creation is slow
• Cost: pay for concurrency
Option 1
Use a SaaS provider

6. (don’t try this at home)
Or roll your own
…

7. Traditional Selenium Grid solution
Option 2

8. Roll your own
Setup Selenium Grid using that old physical server under your desk
or use multiple virtual machines. This will work but:
• Hard to setup
• Difficult to maintain
• Infrastructure is not reusable
Option 2

12. Docker Swarm + Selenium Grid
+

13. Docker swarm + Selenium grid
Architecture

14. • Hub
• Chrome Node
• Firefox Node
• PhantomJS Node
Selenium Docker
Images

15. • Easy to maintain
• Customizable at build time (build-args)
• Customizable at run time (environment variables)
Selenium Images
Versus Virtual Machines

16. “Thats awesome! how
do I set it up ?”
-you

17. services:
hub:
image: selenium/hub:3.1.0
ports:
- 4444:4444
networks:
- grid
Compose Is Your Friend

18. services:
chrome:
image: selenium/node-chrome:3.1.0
depends_on:
- hub
ports:
- "5555:5555"
deploy:
replicas: 1
networks:
- grid
docker-compose.yml

19. services:
firefox:
image: selenium/node-firefox:3.1.0
depends_on:
- hub
ports:
- "5556:5556"
deploy:
replicas: 1
networks:
- grid
docker-compose.yml (cont’d)

20. docker stack deploy docker-compose.yml selenium
Deploy It

21. docker service ls
Great Success!

22. docker service scale chrome=10
Scale It

23. docker service ls
Great Success!

24. 99 problems, but
swarm replicas
ain’t one!

26. • X11 Server (xvfb)
• Builtin VNC Server
(x11vnc)
• Connect and view the
running browser in the
container!
Debug Mode

28. • No Internet Explorer or Safari image
• Hub and node connectivity - tricky
• Nodes can hang
Limitations and Pitfalls
Lessons learned

29. Why Docker?
• Instantaneous grid startup (<10 secs) and teardown
• Speed up execution time 2-3x vs Sass
• Parallel testing scales with your infrastructure
• Sharable infrastructure
• Cost control
Wrap up

30. Thank you!
@docker
#dockercon

32. Section One
1. Agenda item one
2. Agenda item two
3. Agenda item three
4. Agenda item four
5. Agenda item five
Agenda
Section Two
1. Agenda item one
2. Agenda item two
3. Agenda item three
4. Agenda item four
5. Agenda item five

33. Section subhead
Section Header

34. Section subhead
Alt Section
Header

35. Section One
1. Agenda item one
2. Agenda item two
3. Agenda item three
4. Agenda item four
5. Agenda item five
Alt Agenda
Section Two
1. Agenda item one
2. Agenda item two
3. Agenda item three
4. Agenda item four
5. Agenda item five

36. Lorem ipsum dolor sit amet, euismod tincidunt ut. Lorem ipsum
dolor sit amet, euismod tincidunt ut. Lorem ipsum dolor sit amet,
euismod tincidunt ut.
• Bulleted list one
• List item two
• And item number three
Body Slide Title
Subtitle if needed

37. Slide subtitle if needed
The quick brown fox jumps over the lazy dog. The quick brown fox
jumps over the lazy dog. The quick brown fox jumps over the lazy
dog.
• Bulleted list one
• List item two
• And item number three
Alt Background Body Slide

38. Lorem ipsum dolor sit amet,
euismod tincidunt ut. Lorem
ipsum dolor sit amet,
euismod tincidunt ut. Lorem
ipsum dolor sit amet,
euismod tincidunt ut.
Photo Title

39. Lorem ipsum dolor sit amet,
euismod tincidunt ut. Lorem
ipsum dolor sit amet,
euismod tincidunt ut. Lorem
ipsum dolor sit amet,
euismod tincidunt ut.
Photo Title

41. ~/src/docker/expressApp$ docker build -t chrisdias/expressapp
Sending build context to Docker daemon 72.18mb
Step 0 : FROM node:latest
–––> 8e20baae42c8
Step 1: COPY . /src
–––> 8e20baae42c8
Removing intermediate container afdcd49c779
Step 0 : FROM node:latest
–––> 8e20baae42c8
Step 1: COPY . /src
––
demo slide title

42. “Insert quote here!”
Lorem ipsum dolor sit
amet, euismod tincidunt
ut.
-author’s name

43. Thank You Message!
Call to action!
@docker
#dockercon

44. Thank You Message!
Call to action!
@docker #dockercon

45. Session name
Liz Rice
Co-founder and CEO,
Microscalling Systems

46. Session name
Brendan Gregg
Sr. Performance Architect,
Netflix

47. Session name
Brendan Gregg
Sr. Performance Architect,
Netflix
Session name
Liz Rice
Co-founder and CEO,
Microscalling Systems