Use Docker to test microservices
summary
Shows how a CI pipeline uses Docker Compose and an open source Gradle plugin to bring an entire microservice stack up, inject wiremock stubs or a chaos-monkey layer, run JVM unit tests or an executable test image, collect logs and tear down. The build boots the full stack (about three minutes in their run), runs tests against real networked containers, and fails the build on HTTP or exception criteria, enabling feature-branch and repeatable full-stack testing.
AI-written summary · about
chapters (11)
- 0:00Introduction and presenters
- 1:51What is full stack testing
- 7:52Full stack testing demo
- 11:26Preparing the stack with Docker
- 16:25Benefits of Docker images
- 19:57Docker Compose for complex stacks
- 22:23Missing link in toolchain
- 23:07Gradle plugin features
- 33:25Inspecting after tear down
- 35:33Summary and open source tool
- 36:38Q&A session
related talks
28mContinuous Integration Testing: Fully Test your Microservices Application, Early and Often
30mUsing Docker & Compose to Simplify Integration Testing
53mMicroservices Lifecycle Through Docker an CD
30mTest as You Run - Production-like Integration Tests with Docker
41mData Driven and Containerized Testing of Multi Service Networked Systems
40mScala, Docker and Testing oh my!
44mDocker and the Path to a Better Staging Environment
32mUsing Docker in test automation