This message was deleted.

There are multiple ways to achieve this. I m not sure about the best alternative. One of way is to send meta header indicating what sort of response is expected and you can add mapping for the same.

@Kapish Malik can you share an example?

it ll be same mapping. U just need to include header in this example and send header in the request.

@Kapish Malik this is working from postman. It is not working from UITests. I cannot add header

response-type

header. I am using https://github.com/mobileforming/WiremockClient.git. My Stubbing goes like this:

let stub = StubMapping.stubFor(requestMethod: .GET,
                                       urlMatchCondition: .urlPathEqualTo,
                                       url: endPoint)
            .withHeader("response-type", matchCondition: .equalTo, value: "success")
            .willReturn(ResponseDefinition())

I have tried to serve response from local file aprt from this approach. It doesn't work. Can you throw some insights how wiremock pick the response apart from most recent stub?

checking ur example

This stubbing in my unit tests. I am not sending "response-type" in actual request. My request does not "response-type".

apiClient.register {

RESTAPIClient(url: URL(string: "<http://localhost:8080/>")!)

}

func test_02ShouldDisplayBlogList() throws {
        app.launch()
        blogPostListStub.successResponse()
        let cell = app.tables["blogPostTableView"].cells.firstMatch
        XCTAssertTrue(cell.waitForExistence(timeout: 10.0))
    }

ohh okay... it won't work for UT as u need to pass and make code changes in ur existing code.

I was on vacation. sorry for the late respone. I am trying different tests only. I think you got the problem. I cannot modify production code. is there any other way to get the similar behaviour? I tried scenario, It require new state and required state to simulate. Now tests are coupled.

You can always do it by stateful behavior. You can define multiple sequential states which give different responses. https://wiremock.org/docs/stateful-behaviour/