Testing Microservices
summary
Describes a concrete testing approach for a Java microservice called the Liberty starter that the team splits from a monolith into a dedicated zip service and tech services, using JUnit with Gradle/Maven builds, stubs and test doubles, and a standalone test service that exercises REST calls. Five explicit test types are asserted: unit, component, contract, integration and end‑to‑end; contract tests are consumer-driven, integration tests run in staging, Liberty starts fast enough to make component/server tests practical.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:34Katherine Stanley
- 1:07Agenda
- 2:38Liberty Starter
- 5:23Out of Scope
- 5:58What are Microservices
- 9:08Sample Microservice
- 10:12Microservice Anatomy
- 11:29Unit Testing
- 14:10Service Connector
- 17:46Component Test
- 22:50Contract Test
- 25:51Integration Testing
- 29:02Endtoend Testing
- 31:57Recap
- 33:43Add tests for current function
- 35:40Testdriven development
- 38:28Conclusion
- 39:58Extra reading
- 41:20Tools for contract tests
related talks
02h 36mTesting Java Microservice
47mMicroservices Testing with Java
47mBreak Up the Monolith: Testing Microservices
01h 02mMake writing tests more joyful
39mLive Coding: cloud-native application development with MicroProfile and Open Liberty
55mLive Coding: Cloud native Application Development with MicroProfile & Open Liberty
35mMicroservice Testing
37mHow To Build a Test Lib for a Microservice Based Web Application with Geb & Spock
