vodQA(Pune) 2018 - Docker in Testing

1. Docker For
Testing

2. Agenda
I
•Quick Introduction to
Docker
II
•Simplify selenium grid
III
•Containerize test

3. I
•Quick Introduction to Docker

5. Take away
Automation on Different browser using selenium Grid
Challenges :
● Different Browser’s version on Same machine.
● Different OS on same machine.
● Difficult to set up.

6. Are Containers Worth it ?
Google
"Everything at Google runs in a container," Joe Beda, a senior staff software
engineer at Google, explained in some slides shown at the Gluecon
conference this week. "We start over two billion containers per week."
Source: https://www.slideshare.net/brendandburns/gluecon-kubernetes
Uber
We started the migration to Docker in the beginning of 2016, and by now
we are running around 1500 Docker production servers (for MySQL only) and
we have provisioned around 2300 MySQL databases.
Source: https://eng.uber.com/dockerizing-mysql/

8. Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate
your applications from your infrastructure so you can deliver software quickly.

9. Issues with VM

10. Benefits
● Can spin up many containers
● One component, One container
● Throw them away when you’re done
● All the dependencies inside the container

11. Docker file Text editor
Container
Image
Docker repository
Docker run
Docker Push
Docker
build
Imported by Docker file FROM statement
Docker Pull

12. Docker Images
●Docker pull <image_name>
●Docker images

13. Docker Container
● Docker ps –a

14. Docker Network
● docker network ls

15. Docker Volumes
● docker volumes ls

16. I •Simplified Selenium grid

17. Traditional way of setting up Selenium Grid

18. Complications of Selenium grid
• Need of VMs or Physical boxes
• Difficulty in keeping track of machines
• Install software and dependencies

19. Selenium Grid with Docker

20. Images we will use for Selenium grid
• selenium/hub
• selenium/node-phantomjs
• selenium/node-chrome-debug
• selenium/node-firefox-debug
• selenium/node-firefox-debug:3.4.0-bismuth

21. Commands
● docker run -d -p 4446:4444 --name selenium-hub selenium/hub
● docker run -d -P --link selenium-hub:hub selenium/node-chrome-debug
● docker run -d -P --link selenium-hub:hub selenium/node-firefox-debug
● docker run -d -e PHANTOMJS_OPTS="--ignore-ssl-errors=true" --link selenium-
hub:hub selenium/node-phantomjs
Non interactive Port Container Name Image name
Linking with container

22. Further simplify with docker-compose

23. Docker compose file

24. Selenium Grid console – scale any number of nodes

25. I •Containerize tests

26. Selenium Tests

27. Dockerfile
● Docker build –t <image_name>

28. Bring up the Application
● https://github.com/harithah/for_workshop.git
● docker-compose up -d

29. Convert existing tests to access Selenium Grid in Docker
container

30. Access the application

31. Test image inside docker-compose file

32. Volumes

33. Docker compose file with the network configured

34. Commands
● Docker-compose up –d
● Docker ps -a
● Docker-compose scale chromenode=2

35. Sources:
• https://github.com/harithah/ContainerisedTests
• https://github.com/harithah/for_workshop

36. Happy DockerINGGGG!!!!!!!!
Thanks,
Haritha Hari
[Twitter:@HarithaHari1]
&
Manish Hemnani