Make writing tests more joyful
summary
A concrete recipe for testing Jakarta EE microservices using a coffee shop example with two services, Postgres and an async barista with statuses preparing → finished → collected. System tests run as plain JUnit HTTP clients against a running Open Liberty image, with WireMock simulating the barista for async verification and idempotent waits. Emphasizes separate lifecycle for test infra, Open Liberty dev mode for instant code + test turnaround, and use-case/component tests and delegates to keep test code fast, readable and maintainable.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:54Live Demos on Live Coding
- 5:45Using Docker Containers
- 9:38Why Do We Do Testing
- 17:39Create Verify Order Test
- 27:07How To Be More Effective in the Development Workflow
- 34:31Code Level Integration Tests
- 38:02Use Case Tests
- 39:07Test Doubles
- 43:10Integration Tests
- 43:51Takeaways
- 44:22Reusable Components
- 46:15Separate the Life Cycles
- 49:48Reusable Item Potent Test Scenarios
- 50:51Cucumber Test
- 59:23How Do I Measure Code Coverage
related talks
34mWrite tests that spark flow
47mMicroservices Testing with Java
54mExploring Jakarta EE integration testing
56mWrite Tests That Spark Flow
01h 46mHow Java developers should test their applications (RU)
02h 36mTesting Java Microservice
45m12-Factor, Cloud Native Enterprise Java Applications
42mRock-Solid UI and Instrumentation Testing