In MockServer the Java Logger SLF4J binding is only an optional dependency. The simplest approach is to use the Java Logger SLF4J binding. MockServer relies on a SLF4J binding being on the classpath for logs to be output. Test Extension, ClientAndServer or directly using the the project launching MockServer needs to configure the logging MockServer uses SL4J for logging so if MockSever is being launched using the JUnit 4 the JUnit 5 maven or gradle project)Ĭonfiguring logging for JUnit 4 JUnit 5 Test Extension or Java API (i.e. JUnit 4 JUnit 5 Test Extension or Java API (i.e.The following sections explain how to configure logging when running MockServer via:

-Droot.logLevel=OFF - to disable all logging from all other classes.

-Dmockserver.logLevel=OFF - to disable logging from the MockServer and Proxy classes.

To disable logging the following options can be used: The TRACE level logging results in a lot of verbose logging but can be very helpful to debug why a complex matcher (such as the JSON Schema matcher) is not matching.

TRACE - low level details or exceptions that aren't usually considered an error.

DEBUG - all matcher results, including when specific matchers fail (such as HeaderMatcher).

INFO - all interactions with the MockServer including setting up expectations, matching expectations, clearing expectations and verifying requests.

The log can be particularly helpful when trying to debug why a test is failing or

See REST API for full JSON specification LoggingĪll interactions with the MockServer are logged including setting up expectations, matching expectations, clearing expectations and verifying requests.

Var mockServerClient = require('mockserver-client').mockServerClient

Npm config set loglevel