Mock/not-mock response on a per request basis in Integration test.

[sumit singhal]

Hi Team,

I am writing Integration tests. I have a need where for a positive test case request hit an actual service and receive the response. But for a negative test case I must get the mocked response.

I am curious to understand if there is a way that I can mock/not-mock the request on a per configuration basis. Like for example if request accepts email address in request and I provide

1. "inv...@email.com" - response from wire-mock must be a mocked response.
2. "va...@email.com" - mocking must not happen but rather it must hit the actual server to get the response. may be via redirecting or calling the actual service and responding the response to the caller.

Regards,

[thilmano_wiremockuser]

You can tryout "proxyBaseUrl" feature in Wiremock. This would help you implement the Live Invocation

[Tom Akehurst]

You'd need 2 stubs for this:

1) A higher priority (e.g. 5) stub that has a matchesJsonPath body pattern  with an expression matching the email address field you've specified. This should return the negative response status and body you require.

2) A lower priority (e.g. 8) stub that returns a proxy response via the proxyBaseUrl field. In most cases this stub should be made to match any URL and method.