Debug a scenario-Performance Testing(PTS)-阿里云帮助中心

After you configure a performance testing scenario, you can debug it to validate whether the scenario configuration is appropriate. This topic describes how to debug a scenario.

Prerequisites

Create a JMeter performance testing scenario. For more information, see Create a JMeter performance test.

Procedure

PTS consolePerformance testingScene list
In the Actions column of the target scenario, click Edit. On the Edit Scenario page, click Debug Scenario at the bottom of the page to debug the entire scenario.

The debug results show the request logs for all samplers. Click an API to view its debug details.

Note
While waiting for debugging to complete, click the icon in the upper-right corner of the Scenario Debugging dialog box to minimize it. You can then monitor the debug status in the Scenario Debugging floating window in the lower-right corner. Click the floating window again to return to the Scenario Debugging dialog box.

JMeter scenario debug UI

No.	Description
①	The name of the sampler. Click the sampler to view its response details on the right.
②	The response status. This can be a status code (such as 200, 302, 403, 503, or 500) or an exception message. A failed or exception status indicates that no response was received. This might be due to a request timeout or an error in the sampler, such as an unrecognized function or an invalid URL.
③	Request details, including request headers, the structured request body, and the raw request.
④	Response details, including the response header, response body, assertion results, and the raw response.
⑤	The Timing tab displays the duration of the sampler's core lifecycle phases.
⑥	The Trace View tab displays the upstream and downstream trace details for the API under test.
⑦	Engine logs. Click Engine Logs to view information about the performance testing engine.