This message was deleted.

Hi @Shruti Mishra, it’s hard to tell for certain without seeing all the code, but I think one of two things could be happening: 1. You have another (empty) WM instance running and that’s the one your code under test is connecting to, rather than the one you’re start via the JUnit extension. 2. You’re calling some of the code you’re testing before the stubbing call e.g. during initialisation.

Hi @Tom I have added the code snippet above for the code reference, maybe you have referred that. In that wiremockextension instance which I have created above, the same I am referring to, the the stubFor method.

I can’t tell from this how you’re getting the WireMock base URL into your code under test or when/how you’re calling that code, so without being able to see that I can’t suggest anything more specific.

Actually baseUrl is the commented out code @Tom.

That might be the problem then. If you’re not setting the app code’s base URL to one with the dynamically chosen port, it’ll probably default to another, fixed port e.g. 8080 and I’m guessing you have another instance running on that one that has no stubs.

Can you please provide an example of setting base url, earlier I had set it by using properties file, but I guess I did in the wrong manner. Regarding the port, wiremock is running on port 8082, on which no other instance is running which I have verified.

The

.dynamicPort()

in your extension setup will put WireMock on a random port. So it seems whatever is running on 8082 isn’t the one you’re stubbing against.

Actually I saw on the eclipse console, in order to verify on which port it is running...from there came to know 8082...even from cmd I have checked but nothing was running apart from this in 8082 @Tom