Generate Wiremock

Step 2: Learn Existing Patterns

If the project already has WireMock stubs:

• Read src/test/resources/wiremock/mappings/ for mapping format
• Read src/test/resources/__files/ for response body format
• Learn naming conventions, organization, and shared patterns
• Match the exact JSON structure and style

Step 3: Create Stub Files

For each external service call, create:

Mapping file (mappings/[service]/[scenario].json):

{
  "request": {
    "method": "GET",
    "urlPathPattern": "/api/v1/resource/[0-9]+",
    "headers": { "Accept": { "contains": "application/json" } }
  },
  "response": {
    "status": 200,
    "headers": { "Content-Type": "application/json" },
    "bodyFileName": "[service]/[response-file].json"
  },
  "metadata": { "description": "[Clear description]" }
}

Response file (__files/[service]/[response-file].json):

{ "id": 1, "name": "Test", ... }

Step 4: Create All Scenarios

For each service call:

• ✅ Success (200/201)
• ❌ Not Found (404)
• ❌ Validation Error (400/422)
• ❌ Server Error (500)
• ⏱️ Timeout (delay + 200)
• 📭 Empty response (200 with empty body/array)

Step 5: Docker Compose Integration

If docker-compose exists, add WireMock service: