Scrum Gathering Rio 2016 - Containerizing Tests with Docker Compose

Transcript

1. Containerizing Tests with Docker Compose Stefan Teixeira @stefan_teixeira stefanfk@gmail.com stefanteixeira.com.br stefanteixeira.com
2. • QA Automation Engineer @ Toptal • Technical blogs: stefanteixeira.com.br (pt-br) / stefanteixeira.com (en) • Co-organizer of DevOps Carioca and Grupo de Testes Carioca meetups Links: • E-mail: stefanfk@gmail.com • Twitter: twitter.com/stefan_teixeira • LinkedIn: linkedin.com/in/stefanteixeira • GitHub: github.com/stefanteixeira • SlideShare: slideshare.net/stefanteixeira About
3. Docker Compose
4. Docker Compose • Tool for defining and running multi-container applications https://docs.docker.com/compose/
5. Docker Compose • Tool for defining and running multi- container applications • Previously known as Fig https://docs.docker.com/compose/
6. Docker Compose • Tool for defining and running multi- container applications • Previously known as Fig • YAML ❤ https://docs.docker.com/compose/
7. Compose File (v1)
8. Compose File (v2)
9. Containerizing Tests with Docker Compose
10. WAT?
11. Containers != mini-VMs https://twitter.com/rhein_wein/status/662995114235678720
12. Motivation
13. #1 If tests (except unit tests) are hard to run locally, developers will not run them. ¯\_(ϑ)_/¯
14. #2 Sometimes it’s really hard to configure a test environment.
15. “Docker delivers a predictable, reproducible testing environment.” (Laura Frank, Codeship) ❤
16. Examples
17. App A
18. App A DB
19. App A DB Mock Service
20. App A DB Mock Service API Tests
21. App A DB Mock Service API Tests UI Tests
22. App A DB Mock Service API Tests UI Tests Security Tests
23. App A DB Mock Service API Tests UI Tests Security Tests Smoke Tests
24. Demo
25. Demo • Very simple example, with three containers: • App (a REST API) • DB (MongoDB database) • API Tests (written with Supertest) • https://github.com/stefanteixeira/demo-testing- compose
26. Points of attention • Logs
27. Points of attention • Logs • volumes or data containers
28. Points of attention • Logs • volumes or data containers • Startup time
29. Points of attention • Logs • volumes or data containers • Startup time • netcat (nc), curl, wait-for-it, wait_for module (Ansible)
30. Points of attention • Logs • volumes or data containers • Startup time • netcat (nc), curl, wait-for-it, wait_for module (Ansible) • Generating images
31. Points of attention • Logs • volumes or data containers • Startup time • netcat (nc), curl, wait-for-it, wait_for module (Ansible) • Generating images • Alpine-linux, Phusion (minimal base images)
32. Points of attention • Logs • volumes or data containers • Startup time • netcat (nc), curl, wait-for-it, wait_for module (Ansible) • Generating images • Alpine-linux, Phusion (minimal base images) • Automate the process
33. References • "Stop Being Lazy and Test Your Software”: • https://www.youtube.com/watch?v=Mx1Il9wIepw • http://www.slideshare.net/rheinwein/stop-being-lazy-and-test- your-software • https://hharnisc.github.io/2016/06/19/integration-testing-with-docker- compose.html • https://docs.docker.com/compose/startup-order/ • https://github.com/vishnubob/wait-for-it • https://www.ansible.com/blog/six-ways-ansible-makes-docker- compose-better
34. Thanks! Stefan Teixeira @stefan_teixeira stefanfk@gmail.com stefanteixeira.com.br stefanteixeira.com