How can Docker improve your team's dev speed by improving your integration tests infrastructure?

1. Docker
fast dev faster testing

2. Why this enthusiasm?

3. This means...
37 vs. 536
Running on a 16 gb ram server...

4. Also...

5. Integration tests
1. First level of testing that validates layers / integration
between them
2. Perhaps the most valuable tests for dev
3. Runs in mins
4. Environment is smaller, controlled than a E2E
5. Runs on every developer laptop

6. Component
Under Test
Test
Dependency
A
Mocked
Dependency
B
Integration test anatomy
Layer1 Layer2 JBoss DB

7. But there are many many challenges….

8. It works only on my machine!

9. They are too slow to run

10. Why so slow?
Infrastructure /
deployment Execution
99% 1%

11. DBJboss
A proposal: Docker images
Cache
Network
Simulator

12. Better integration tests
Faster setup, easier to develop ⇒ test cycle.
Everything runs on your laptop, but everything is disposable: when the tests
are over you just kill the containers. When you want them back, they come
fresh.
Same tests will run on Jenkins after a commit

13. Single command brings it all
docker-compose up

14. Benefits
1. Decoupled test infrastructure from test suite
2. Core developers maintain the infra. Others just use it
3. Standard environment. Runs on CI!
4. Tests run faster. More tests run throughout the day

15. “At the end of the day, you become a better developer.
There is no magic. The container’s recipes are on your
laptop. They are code.”

16. Quick demo...

17. Discussions

18. “Simplicity is the ultimate sophistication.”
Leonardo Da Vinci