TRANSPARENT PROXY AND SERVICE STUB: WILMA
summary
WILMA implements a transparent proxy that clones and logs requests and a configurable stub that returns prerecorded or generated replies, supporting HTTP/HTTPS and two-way SSL interception, JSON/XML payloads and plugin extensions. It stores request/response pairs, scales to tens of thousands of messages (example shows ~15–25k with automatic cleanup), provides Java and .NET client libraries, a web UI, a Docker image and GitHub repo, and proves useful in CI by letting development continue when third-party services are unavailable — it works in productionlike tests.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:37THE TEST SITUATION-COMPONENTISERVICE
- 4:34THE TEST SITUATION - COMPONENTISERVICE/MICROSERVICE
- 5:05EXPECTATIONS (REQUIREMENTS)
- 6:40SOLUTION: WILMA
- 6:59HOW WILMA WORKS? - Information-flow Diagram
- 7:20HOW WILMA WORKS? - Handling a Request as Proxy
- 10:08HOW WILMA WORKS? - Configuring the Stub Service
- 11:09HOW WILMA CAN BE USED?
- 12:41OPERATION MODE - Exclusive PROXY Mode
- 13:29OPERATION MODE - Exclusive STUB Mode
- 15:29WHAT WILMA OFFERS IN ADDITION?
related talks
33mSmart Integration Tests with Smart Mocks
32mWiremock: because your microservice needs a buddy when you're testing
41mAdvanced HTTP Mocking with
36mWebmock unmocked
38mDoublers in Tests. Wiremock vs Mockito
31mThe power of mocking APIs
24mWebMock Unmocked
40mStrategic Business Functionality Testing: Accelerating Development Through Mocking