Wiremock: because your microservice needs a buddy when you're testing
summary
WireMock runs as a standalone WireMock process on a port and records real API traffic into editable mapping JSON files so tests replay deterministic responses instead of hitting flaky dependencies. Demo shows proxying to an external weather API (limited to 100 calls/day), using record-mappings + proxy to capture live responses, then enabling global response templating and custom transformers to inject query params, generate random-ish temperature values, and support scenarios, state and error cases for stable microservice tests.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:20About me
- 1:03Why Wiremock
- 1:39Problems with testing
- 4:09Types of test doubles
- 5:51Wiremock
- 6:17Benefits
- 7:43Wiremock Overview
- 9:09Wiremock Standalone
- 9:40Demo
- 13:57Port
- 14:51Admin
- 16:15Weather API
- 19:05Cold weather
- 19:20Static URL
- 19:39Request with interests
- 19:57Why is it like this
- 20:25We both know
- 23:51Watermark
- 27:03Random values
- 28:54Temperature
- 30:17My experiences
related talks
41mAdvanced HTTP Mocking with
31mThe power of mocking APIs
38mDoublers in Tests. Wiremock vs Mockito
51mFramework agnostic REST api testing
13mSpeed up writing tests with Wiremock Spring Boot
42mFree Your Frontend Client from Backend Cage
44mFake It until You Make It! API Integration Testing with Containers & WireMock
25mMock to start