With New Test Create (NTC), we are introducing the Debug Test feature.
Note: The Debug Test feature is new to the V4 (version 4) update and replaces the now-deprecated V3 sandbox feature. Debug Tests are only available in V4. Please check out our guide on the Benefits & Advantages of Blazemeter's New Infrastructure and UI for more details.
Run a Debug Test
To run a this test option, just click the blue "Debug Test" button:
Then, it creates a low-scale test run that you can use to validate your configuration:
Rather than alter your test configuration, this feature makes a logical copy of your test, and runs it at a lower scale. The test will run with 10 threads, and for a maximum of 5 minutes or 100 iterations, whichever occurs first.
Any test initiated by clicking the "Debug Test" button, will be considered as 'free', and will not charge a credit or VUH (Virtual User Hours) for the test run.
Notice: Did you encounter the following error when starting a debug test:
Bad Request: Multiple scenarios are not supported in Debug mode - Click here for more details
Viewing Results of Debug Test Runs
To view the results of Debug Test runs, navigate to the 'History' section in the Test Configuration page, and click the "Debug" toggle:
When toggled to "Debug", you will see your Debug Test runs, as displayed below:
Viewing Detailed Request/Response Data
Detailed request and response information can be found in the 'trace.jtl' file, which is added to the artifacts.zip file for "Debug Test" runs.
NOTE: These "Debug Test" runs do not appear in test trends, the Reports drop-down menu, or "Show All Reports" lists. Also, they do not enforce, or display a "Passed/Failed" status. Last, the data for "Debug Test" runs is deleted after 30 days.