Write tests that spark flow
summary
Shows how to write maintainable system/acceptance tests for a Java microservice using Quarkus, JUnit, Docker and Kubernetes; runs a realistic setup of three containers (coffee shop, barista, database) and uses WireMock to stub the barista. Tests use delegation so high-level steps like create order espresso colombia and verify order status hide HTTP/JSON details. Quarkus dev mode gives sub‑5s restarts for fast feedback, tests run locally or against a Kubernetes deployment and the approach proves reusable and fast. WireMock Quarkus dev mode
AI-written summary · about
chapters (23)
- 0:00Introduction
- 2:13Coffee example
- 3:02Build locally
- 3:57Match production
- 4:35Docker containers
- 5:02Orders
- 5:52Origin
- 6:51Validate
- 8:36How this works
- 9:27Why this is running
- 9:48Verify in Java
- 11:10Is this good idea
- 11:57The challenge
- 13:35Pseudocode
- 13:56Start from the beginning
- 16:29Create verify order
- 17:23System test implementation
- 18:47System test environment
- 19:28Mock server technology
- 21:16Running tests
- 23:20Running tests in development mode
- 24:30The perfect setup
- 27:10Reuse the system test
related talks
56mWrite Tests That Spark Flow
26mStreamlining Cloud-Native Development: Simplifying Dependencies and Testing with Microcks
48mIntegration Testing with Quarkus.
30mTest-Driven Development: It's easier than you think!
47mProd like Integration Testing for Cloud Native Microservices
46mSupersonic Subatomic Mocking: How to test your Quarkus app
01h 02mMake writing tests more joyful
44mQuarkus: Supersonic, Subatomic Full-Stack Development