The document discusses how Docker can be used for integration testing. It describes how Docker allows running production environments locally, creating proofs of concept, and avoiding port collisions in continuous integration environments. It also outlines how Docker commands like build, run, start, stop, link, expose, and tag can fit into different steps of a build process. Finally, it introduces the docker-maven-plugin for building Docker images and integrating Docker into the Maven build lifecycle for testing.

1. Docker for Integration
Testing
Wouter Danes
Docker Amsterdam / Utrecht, 28 August 2014

2. API Platform
Engineer

3. Agenda
• Ways I use docker during development
• Fitting docker into your build process
• Docker maven integration

4. Ways I use docker during development

5. Shadow IT

6. Run !
“production” !
locally

7. Proofs!
of!
Concept

8. CI environment
• Spawn build slaves
• No port collisions
• Replace D/T with feature branch deploys
• No version / stack collisions in “environment”

9. Fitting docker into your build process

10. High level build process
build test package test
package
publish

11. Docker commands per build step
build test package test
package
publish
build run
start
stop
link
expose
tag
push

12. Docker maven integration

13. build test package test
package
publish
build run
start
stop
link
expose
tag
push
resources
compile
test package integration-test
verify
install
deploy
Maven vs Docker

14. docker-maven-plugin
• Build docker images
• Start containers
• Link containers
• Wait for containers to finish initialisation
• Expose URLs / port info to integration tests
• Clean up
• Push images to an index / registry

15. Demo project

16. References
• Two docker blog posts:
www.wouterdanes.net
• Docker maven plugin:
github.com/wouterd/docker-maven-plugin
• 12 principles for developing containers well:
12factor.net