From 2a3495f80a31c126487f91c2f4aa79e726d7510b Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Mon, 31 Jul 2017 16:28:51 +0200 Subject: [PATCH] Updated docs --- README.adoc | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/README.adoc b/README.adoc index 2cf991def5..b064fefa72 100644 --- a/README.adoc +++ b/README.adoc @@ -1339,6 +1339,20 @@ The generated tests all boil down to RestAssured in some form or fashion which r logging.level.org.apache.http.wire=DEBUG ---- +==== How can I debug the mapping/request/response being sent by WireMock? + +Starting from version `1.2.0` we turn on WireMock logging to +info and the WireMock notifier to being verbose. Now you will +exactly know what request was received by WireMock server and which +matching response definition was picked. + +To turn off this feature just bump WireMock logging to `ERROR` + +[source,properties,indent=0] +---- +logging.level.com.github.tomakehurst.wiremock=ERROR +---- + ==== How can I see what got registered in the HTTP server stub? You can use the `mappingsOutputFolder` property on `@AutoConfigureStubRunner` or `StubRunnerRule`