Hi All - I'm trying to get started with wire Mock - i'm using it with Junit 4. I'm quite new to the world of Sping / Java so i'm following this guide here: https://wiremock.org/docs/quickstart/java-junit/ and i think the example code seems invalid...First up: am I right in thinking this:

@Rule
public WireMockRule wireMockRule = new WireMockRule(8089); // No-args constructor defaults to port 8080

Should be just:

@Rule
public WireMockRule wireMockRule;

(the documented code seems to blow up) also, in this line:

.uri(wiremockServer.url("/my/resource"))

what's wiremockServer ? where do i instantiate that? does the @Rule not take care of that for me? also, when my code reaches

stubFor(post("/my/resource")

It just blows up at that very point with a connection refused to http://localhost:8080 i don't quite know what i'm doing wrong - is that particular bit in the documentation correct?

Hi, when you say the documented code blows up, could you provide an example of the error ?

ah the blow up when I do this: @Rule public WireMockRule wireMockRule = new WireMockRule(8089) Is an index out of bounds exception. i'm using junit 4.13.2 becuase i couldn't find v5 in our repo. however i've just this second discovered that it's actually called junit5 and is located somewhere else I canget to so i'll try with that

If it is a

3.x.x

spring boot project then it is probably worth looking at jUnit 5 (junit jupiter) for testing. We have just adopted a spring boot integration project wicch provides much better support - especially for Jetty 12 (which is what Spring Boot 3.x.x ships with)

ace, cheers - it is indeed an SB 3 project so I'll get digging into the official SB 3 integration thanks.

No worries. Enjoy

OK junit5 is a goer but can't do the SB integration yet due to some internal rules here. So This code Here

@WireMockTest

public class MockServerTest {
  
  @Test
  public void testMockServer(WireMockRunTimeInfo wireMockRuntimeInfo) {
    stubFor(get("/do/ping").willReturn(ok()));

  }
}

I haven't used spring for a while but are you sure the junit version is correct ? I thought all the junit 5 versions started with 5 ? It should be a junit jupiter version that you are using if I remember correctly

ok yep my error there - defo using junit-jupiter 5.10.5 now. still getting error index out of bounds on that small code snippet. have tried the above code with the jetty-12. It seems the

@WireMockTest

How have you added the wiremock dependency ?

in pom.xml

Can you paste the dependency here ?

<dependency> <groupId>org.wiremock</groupId> <artifactId>wiremock-jetty12</artifactId> <version>3.10.0</version> </dependency>

Cool, so you are using the jetty 12 dependency. Could you post the stacktrace ?

image.png

That is a little strange. I have just updated the example to spring boot

3.4.1

and wiremock

3.10.0

and the tests seem to pass fine.

cool - downgrading to 3.9.2 it works.

That is good news, although I would still love to know what the issue with the latest version is 🙂

worth noting though this is spring 3.3...should have said before!

No worries. Just out of interest what is the version of spring that you are using ?

it is spring-core 6.1.14

Not sure I understand. Is your wiremock instance not running on

localhost

? Normally the tests just assume localhost and stub a url off of that I think. Pretty much like this example - https://github.com/wiremock/wiremock-examples/blob/main/spring-boot/spring-boot-3/[…]mockexamples/wiremockjetty12/PeopleInSpaceIntegrationTests.java

i got you. yeah it's just that i'm being picky. whilst they're running on localhost i was wanting a different name for it, where i could call it https://api-a but it would still end up on my localhost. no matter. Cheers foryour help.

That might be possible. I would need to look at the code. You can specify the bind address in the options when you configure wiremock:

// Bind the WireMock server to this IP address locally. Defaults to the loopback adaptor.
.bindAddress("192.168.1.111")

If you are specifying a name (dns) for the base url, that would still need to be configured locally to point to 127.0.0.1. You would then run into trouble if you wanted to run the same test in a CI server or someone else on their machine who didn't have the same local config for the dns name