You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>All interactions with the MockServer are logged including setting up expectations, matching expectations, clearing expectations and verifying requests. The when running from the command line, Maven plugin, Grunt plugin or npm module the log is written to a file called <strong>mockserver.log</strong> in the current working directory where the MockServer is running. This log can be particularly helpful when trying to debug why a test is failing or expectations are not being matched.</p>
439
+
<p>All interactions with the MockServer are logged including setting up expectations, matching expectations, clearing expectations and verifying requests. The when running from the command line, Maven plugin, npm module or Grunt plugin the log is written to a file called <strong>mockserver.log</strong> in the current working directory where the MockServer is running. This log can be particularly helpful when trying to debug why a test is failing or expectations are not being matched.</p>
440
440
441
441
<p>The system property <spanclass="inline_code">mockserver.logLevel</span> can be used to set the <ahref="/mock_server/debugging_issues.html#logging-levels">log level</a>, as shown above.</p>
Copy file name to clipboardExpand all lines: jekyll-www.mock-server.com/mock_server/_includes/running_mock_server_summary.html
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,8 @@ <h3>The MockServer and MockServer Proxy can be run:</h3>
6
6
<li>using a <ahref="/mock_server/running_mock_server.html#junit_rule"><strong>JUnit @Rule</strong></a> via a <spanclass="annotation">@Rule</span> annotated field in a JUnit test</li>
7
7
<li>from the <ahref="/mock_server/running_mock_server.html#running_from_command_line"><strong>command line</strong></a> as a stand-alone process in a test environment</li>
8
8
<li>as a <ahref="/mock_server/running_mock_server.html#deployable_war"><strong>deployable WAR</strong></a> to an existing application server</li>
9
-
<li>as a <ahref="/mock_server/running_mock_server.html#mockserver_grunt"><strong>Grunt plugin</strong></a> as part of a Grunt build cycle</li>
10
9
<li>as a <ahref="/mock_server/running_mock_server.html#mockserver_grunt"><strong>Node.js (npm) module</strong></a> from any Node.js code</li>
10
+
<li>as a <ahref="/mock_server/running_mock_server.html#mockserver_grunt"><strong>Grunt plugin</strong></a> as part of a Grunt build cycle</li>
11
11
<li>as a <ahref="/mock_server/running_mock_server.html#docker_container"><strong>Docker container</strong></a> in any Docker enabled environment</li>
12
12
</ul>
13
13
@@ -17,8 +17,8 @@ <h3>MockServer and MockServer Proxy is available as:</h3>
17
17
<li>a stand alone <ahref="http://search.maven.org/remotecontent?filepath=org/mock-server/mockserver-netty/4.0.0/mockserver-netty-4.0.0-jar-with-dependencies.jar">Netty web server</a> that is fully self contained</li>
18
18
<li>a <ahref="http://search.maven.org/remotecontent?filepath=org/mock-server/mockserver-war/4.0.0/mockserver-war-4.0.0.war">deployable WAR</a> that runs on any JEE web server</li>
<p>To start or stop the MockServer from any Node.js code you need to import this module using <spanclass="inline_code">require(<spanclass="string_literal">'mockserver-grunt'</span>)</span> as follows:</p>
9
+
<p>To start or stop the MockServer from any Node.js code you need to import this module using <spanclass="inline_code">require(<spanclass="string_literal">'mockserver-node'</span>)</span> as follows:</p>
<p>Then you can use either the <spanclass="inline_code">start_mockserver</span> or <spanclass="inline_code">stop_mockserver</span> functions as follows:</p>
Copy file name to clipboardExpand all lines: jekyll-www.mock-server.com/mock_server/debugging_issues.html
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ <h2>Logging</h2>
37
37
38
38
<p>The <strong>TRACE</strong> 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.</p>
39
39
40
-
<p>When MockServer is run from the command line, Maven plugin, Grunt plugin or npm module the log is written to a file called <strong>mockserver.log</strong> in the current working directory where the MockServer is running.</p>
40
+
<p>When MockServer is run from the command line, Maven plugin, npm module or Grunt plugin the log is written to a file called <strong>mockserver.log</strong> in the current working directory where the MockServer is running.</p>
<p>When running MockServer using the <ahref="/mock_server/running_mock_server.html#mockserver_grunt"><strong>mockserver-grunt</strong></a> Grunt plugin and Node.js (npm) module the <spanclass="inline_code">verbose</span> option can be used to enable <strong>INFO</strong> level logging and the
108
-
<spanclass="inline_code">trace</span> option can be used to enable <strong>TRACE</strong> level logging. In addition the <spanclass="inline_code">--verbose</span> command line flag can be used for Grunt builds to enable the <strong>mockserver-grunt</strong> verbose option dynamically.</p>
107
+
<p>When running MockServer using the <ahref="/mock_server/running_mock_server.html#mockserver_grunt"><strong>mockserver-node</strong></a> Grunt plugin and Node.js (npm) module the <spanclass="inline_code">verbose</span> option can be used to enable <strong>INFO</strong> level logging and the
108
+
<spanclass="inline_code">trace</span> option can be used to enable <strong>TRACE</strong> level logging. In addition the <spanclass="inline_code">--verbose</span> command line flag can be used for Grunt builds to enable the <strong>mockserver-node</strong> verbose option dynamically.</p>
<p>To debug the Grunt plugin or npm module you need to provide the <spanclass="inline_code">javaDebugPort</span> option. This option will enable the following command line switch <spanclass="inline_code">'-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=' + options.javaDebugPort</span>.</p>
212
+
<p>To debug the npm module or Grunt plugin you need to provide the <spanclass="inline_code">javaDebugPort</span> option. This option will enable the following command line switch <spanclass="inline_code">'-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=' + options.javaDebugPort</span>.</p>
213
213
214
214
<p>For example debug <strong>node module</strong>, as follows:</p>
<li><ahref="https://www.npmjs.org/package/mockserver-grunt">mockserver-grunt</a> - node module and grunt taks to start and stop MockServer and its proxy <ahref="http://badge.fury.io/js/mockserver-grunt"><imgsrc="https://badge.fury.io/js/mockserver-grunt.png" alt="npm version" height="18"></a> <ahref="http://badge.fury.io/bo/mockserver-grunt"></a></li>
18
+
<li><ahref="https://www.npmjs.org/package/mockserver-node">mockserver-node</a> - node module and grunt taks to start and stop MockServer and its proxy <ahref="http://badge.fury.io/js/mockserver-node"><imgsrc="https://badge.fury.io/js/mockserver-node.png" alt="npm version" height="18"></a> <ahref="http://badge.fury.io/bo/mockserver-node"></a></li>
19
19
<li><ahref="https://www.npmjs.org/package/mockserver-client">mockserver-client</a> - node client for MockServer and its proxy <ahref="http://badge.fury.io/js/mockserver-client"><imgsrc="https://badge.fury.io/js/mockserver-client.png" alt="npm version" height="18"></a> <ahref="http://badge.fury.io/bo/mockserver-client"></a></li>
0 commit comments