Question about the functionality of WireMock

[Артём Ульянов]

Hello! Earlier (in version 2.24.1) there was such functionality that if, when accessing a stub, some parameters were not matched by patterns (for example, the "test" heading should be equal to "123"), then information about the nearest stubs that fit for this request, will be output to the console (this table is visible on the screenshot).
In new versions, there is no such table, and the question is how to activate it so that in the event of a 404 error, a similar table is displayed.
I am using Spring Boot and building my application on top of your library.

That is, I launch the framework using WireMockHandlerDispatchingServlet, setting up the class WireMockApp and e.t.c.

[Tom Akehurst]

The diff table you're describing is still present in the latest version of WireMock and by default it is written on the HTTP response and to the log.

Perhaps something about the way you have WireMock integrated into Spring is suppressing it from the output?

[Tom Akehurst]

The diff is now logged at error here:

https://github.com/wiremock/wiremock/blob/master/src/main/java/com/github/tomakehurst/wiremock/verification/notmatched/PlainTextStubNotMatchedRenderer.java#L58

If Spring or some other library is configuring the logger to suppress this, then that might be the reason.

Also, since it's also written in the response body you can always get at it by logging from your app's HTTP client.