Ensure parallel execution of tests and mocking

Hello,

I like the kind of WireMock for stubbing and testing. Nice work! Much better than starting the old sun lib HttpServer 😉

I’m currently using WireMock for mocking service calls and testing http clients. As test suite I take TestNG. The test suite can be executed parallel and several client tests are running at the same time. Each test instantiates a WireMock server and ends it after the test class is done.

The problem is, that the static instance of WireMock is not suitable for multiple threads.

private static WireMock defaultInstance = new WireMock();

To solve this problem I suggest to add another method on instance level, like this:

WireMock wm =  WireMock.createInstance(); 
wm.stubFor();
wm.verify();

Alternatively, the ‘stubFor()’ and ‘verify()’ methods take their instance from a ThreadLocal variable.

What do you think about the suggestions?

Thanks Olli

[jamietanna]

Hey @swtestacademy mind raising a separate issue for us to discuss that in? 🙏

[swtestacademy]

Hi all,

Is there any way to create a new wiremock instance when we are using @AutoConfigureWiremock annotation?

I solved the dynamic port issue but when I am using @AutoConfigureWireMock annotation with JUnit 5, I could not create multiple instances and tests are failing in parallel execution.