Debug scenarios

1. Assertion results

   An 'x' icon indicates an exception. Select the API to view the response details on the right.

2. Response status

   The status can be a status code (such as 200, 302, 403, 503, or 500) or an Abnormal message. An Abnormal message means no response was received. This may be caused by a request timeout or an error in the request URL or body, such as an unrecognized function or an invalid URL format.

   Note

   You can view the request and response details for each debugged API. To troubleshoot these issues, check the following:

   • If the response status is Abnormal, check the exception details in the error information section of the Response Details tab. For example, the exception can be caused by invalid parameters, such as the invalid use of a system function.

   • If the response status is a status code other than 200, check the returned information and perform standard troubleshooting by using the logs on your server.

   • If an assertion fails, check the assertion details in the Check Point Information section of the Response Details tab. If the current value is empty, no output parameter value was extracted.

3. Error information

   This section displays details about abnormal responses, such as timeouts, parameter errors, or connection rejections.

4. The Timing tab details the time taken during the core lifecycle of a request.

   You can use the Timing waterfall model to view error information. All errors appear in the Timing waterfall model.

   For example, if you enable 302 redirection in the scenario settings, you can check the Timing waterfall model to see if a redirect occurred and its specific path.

5. Test an output parameter expression

   When you need to extract a specific string from the response details of a request, typically from a text-based response body, you can test a regular expression in the debugging window to check if it is correct. You can also reset the output parameter as needed.

   Note

   This feature is not available for JSON formats of the application/json and text/json types because these formats are easy to parse.

   1. In the Debug Scenario dialog box, select an API on the right and click Click to test the regular expression for the output parameter.

   2. In the Test output parameter regular expression dialog box, select a source format, enter a regular expression, and specify the Nth match. Then, click Test Expression. Use the matching result in the response details to verify that the extracted content is as expected.

   3. If you need to reset the output parameter, click Sync Output Parameter to synchronize the regular expression to the output parameter list of the API.

      Note

      If you synchronized an output parameter during debugging, return to the scenario settings tab of the stress testing scenario and set a name for the output parameter on the Output Parameter Definition tab of the API.

Click a Sampler to view the details of requests and responses and the Timing waterfall model in the sampling log area.

• Sampling log:

  • The General tab displays the request URL, request method, and request status code.

  • The request details tab displays the request headers, body, and the original packet.

  • The Response Details tab displays the response headers, body, and the original packet.

  • The Timing tab displays the time taken for each API.

• The Engine Logs area displays the JMeter runtime logs. If no sampling log is generated after you debug the script, you can analyze and troubleshoot issues using the error information in the engine logs. For more information about common errors and their causes, see Common Errors.