Hi I ve been using WireMock for some testing and I had a req WireMock #wiremock-java

Hi. I've been using WireMock for some testing and...

Neal Hawman

01/18/2023, 3:22 PM

Hi. I've been using WireMock for some testing and I had a requirement for a web service to keep looping round whenever it gets a 429 error until the target web site corrects itself and returns a 200. I was wondering if there was any way to simulate this in the WireMock JSON configuration files. I know there is an __admin/requests/count endpoint but that will just tell me the number of requests that have been made at a given time. I want to put a condition in the config file so that e.g. on the first 4 calls, the mock returns 429 but on subsequent calls it returns 200.

Tom

01/18/2023, 3:46 PM

Hi @Neal Hawman you can use scenarios to create a sequence of responses for a given request, so you could set it up to do 429, 429, 429, 200 or something like that.

Neal Hawman

01/19/2023, 9:09 AM

Thanks. Is there a way to move automatically from one scenario state to the next? From the documentation it looked as if you had to change the state by sending a web request.

Tom

01/19/2023, 9:21 AM

By setting the

newScenarioState

attribute on the stub, calling that stub will automatically advance the scenario’s state. Here are the relevant docs: https://wiremock.org/docs/stateful-behaviour/

Tom

01/19/2023, 9:24 AM

Here’s a full example of how to do what you’re looking for:

Copy code

{
  "mappings": [
    {
      "scenarioName": "rate-limiting",
      "requiredScenarioState": "Started",
      "newScenarioState": "error-1",
      "request": {
        "method": "GET",
        "urlPath": "/something"
      },
      "response": {
        "status": 429,
        "body": "Too fast!"
      }
    },
    {
      "scenarioName": "rate-limiting",
      "requiredScenarioState": "error-1",
      "newScenarioState": "error-2",
      "request": {
        "method": "GET",
        "urlPath": "/something"
      },
      "response": {
        "status": 429,
        "body": "Too fast!"
      }
    },
    {
      "scenarioName": "rate-limiting",
      "requiredScenarioState": "error-2",
      "newScenarioState": "success",
      "request": {
        "method": "GET",
        "urlPath": "/something"
      },
      "response": {
        "status": 429,
        "body": "Too fast!"
      }
    },
    {
      "scenarioName": "rate-limiting",
      "requiredScenarioState": "success",
      "request": {
        "method": "GET",
        "urlPath": "/something"
      },
      "response": {
        "status": 200,
        "body": "OK"
      }
    }
  ]
}

Neal Hawman

01/19/2023, 9:32 AM

Many thanks. That's sounds like exactly what I want.

👍 1

4 Views

Open in Slack

Previous Next