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
Rainer Jung (Bug 52497):
Some improvements for DebugSampler and DebugPostProcessor:
set reponse code and message using setResponseOK()
When doing web testing, one often adds a global reponse assertion testing for the HTTP status code. Currently those elements do generate a sampler result without setting the code. Thus they are shown as red in the results tree.
add output data available in DebugSampler also to DebugPostProcessor
PostProcessors can be defined globally and JMeter automatically adds them to each Sampler. A similar feature for Samplers does IMHO not exist. When debugging a test plan, it is useful to have the full output of variables and properties available after each sample. An easy way to di it, is adding this data to DebugPostProcessor and then defining that DebugPostProcessir globally in the plan. When the plan works, one can simply disable the DebugPostProcessor.
I made all four types of data configurable similar to DebugSampler and added the properties for various languages:
Sampler Properties (default true)
JMeter Properties (default false)
JMeter Variable (default true)
System Properties (default false)
sort the sampler properties output in DebugPostProcessor
add sample start and end to the sample generated by the DebugPostProcessor
One thing is not contained in the patch:
update docs including screenshots
Finally a warning: a globally defined PostProcessor will IMHO always run before any PostProcessor explicitely added to a sampler. So a globally defined DebugPostProcessor will e.g. not correctly show the result of a JMeter variable just extacted via a reular expression from a sample. It will only show that variable correctly in the output for the following sampler.
Don't know whether there's a way to influence the order, but IMHO it's not a showstopper, because one can look up the values in the next sampler's DebugPostProcessor output.
Rainer Jung (Bug 52497):
Some improvements for DebugSampler and DebugPostProcessor:
When doing web testing, one often adds a global reponse assertion testing for the HTTP status code. Currently those elements do generate a sampler result without setting the code. Thus they are shown as red in the results tree.
PostProcessors can be defined globally and JMeter automatically adds them to each Sampler. A similar feature for Samplers does IMHO not exist. When debugging a test plan, it is useful to have the full output of variables and properties available after each sample. An easy way to di it, is adding this data to DebugPostProcessor and then defining that DebugPostProcessir globally in the plan. When the plan works, one can simply disable the DebugPostProcessor.
I made all four types of data configurable similar to DebugSampler and added the properties for various languages:
Sampler Properties (default true)
JMeter Properties (default false)
JMeter Variable (default true)
System Properties (default false)
sort the sampler properties output in DebugPostProcessor
add sample start and end to the sample generated by the DebugPostProcessor
One thing is not contained in the patch:
Finally a warning: a globally defined PostProcessor will IMHO always run before any PostProcessor explicitely added to a sampler. So a globally defined DebugPostProcessor will e.g. not correctly show the result of a JMeter variable just extacted via a reular expression from a sample. It will only show that variable correctly in the output for the following sampler.
Don't know whether there's a way to influence the order, but IMHO it's not a showstopper, because one can look up the values in the next sampler's DebugPostProcessor output.
Regards,
Rainer
Created attachment DebugSampler_DebugPreProcessor.patch: Implementation of improvements
Version: Nightly
OS: All
The text was updated successfully, but these errors were encountered: