JMeter – Debug PostProcessor
The problem in the main sample is located using the JMeter debugging post-processor. The ‘View Result Tree’ shows the output of the debugging post-processor. Essentially, Debug PostProcessor returned 4 attributes, which are explained in the text below.
How do I add ‘Debug PostProcessor’?
You can follow the following steps:
- Select the ‘Sampler’ element to which you want to add this post-processor
- Right-click on the swatch
- Mouse over ‘Add’
- Move your mouse over ‘Post Processors’
- Click ‘Debug Post Processor’
What are the ‘Debug PostProcessor’ input fields?
1.JMeter properties: Enabling this option allows you to see the properties that JMeter uses when it runs the test. User.properties, system.properties, and others are some of the crucial properties. You can check the value of any property that has passed the test if you think there is a problem with the JMeter properties. See the image below for a full list of JMeter attributes that are generated by the debugging post-processor. The default value of this attribute is False.
2.JMeter variables: This attribute’s default value is False. To obtain the values of JMeter variables, this option is enabled. The JMeter Thread, sampler start time, etc. can all be checked here.
3. Sampler attributes: This attribute demonstrates the main purpose of the debugging postprocessor. The default value for the sampler properties is True, which displays all the properties of the main sampler, including host, port, host attributes, etc. For the full list of sampler properties that the debug post runs, see the screenshot below.
4. System characteristics Due to the extensive information about the system (the machine on which the test is run), such as the OS name, OS version, java version, user information, etc., this attribute is by default set to False.
