URL Not Matching about wiremock

[tomakehurst]

Hi Toby,

Could you give me a little more detail?

Is it the verify call or a stub that's failing?

Tom

[tomakehurst]

Sorry, just noticed you've already closed this!

[tobyweston]

Hi Tom,

Not sure what was going on in the end. My tests started passing and I've no clue what's going on! Hence I closed it.

Don't worry, if I encounter more problems, I'll repost with more details.

One thought though, I do seem to get intermittent results. I'll have to find out more before I can comment properly, but have you noticed problems with the statics and running in multithreaded envs? EDIT: <- that last line's prob not true, it's more likely I'm running into race conditions of my own making!

Thanks

[tomakehurst]

I have to admit I've not run it a huge amount with test multi-threading (presume this is what you mean?). It's designed with that in mind, but I've never got round to writing a proper set of concurrency tests.

I'd be interested to hear about what you're seeing and in what context.

[tobyweston]

I'm running into standard race conditions, so not really a wiremock issue. The usual thing really, making a request in the UI, verifying that the stubbed (by wiremock) endpoint got called and forgetting that the "making a request" part is in a browser/JavaScript and is asynchronous!

In my tests, I've added code to probe for wiremock verifications to get round it. If you're interested, it used this and an example is here.

[tomakehurst]

I'm considering writing a multi-threaded JUnit rule that spins up a wiremock instance per-thread on a separate port. The advantage would be that you don't get requests from another thread in the verify log and you don't inadvertently match stubs configured in other threads.

Do you think this would be any help?