Bug 59696 - Suppress output of GET HTTP Requests
Summary: Suppress output of GET HTTP Requests
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 3.0
Hardware: PC All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-13 18:10 UTC by John Pierce
Modified: 2016-06-14 09:25 UTC (History)
1 user (show)



Attachments
Example of Sampler HTTP Request Output (image) (117.17 KB, image/jpeg)
2016-06-13 18:24 UTC, John Pierce
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Pierce 2016-06-13 18:10:50 UTC
Some HTTP Requests are better than others.
For example, I use a lot of REST init-config GET to fill a form,
and then submit the form PUT to create a new record with the next HTTP request.

This is especially helpful for html report writer where I only need to see the PUT records, and not the GET records. Either configurable, or an additional checkbox to the HTML Request Dialog.

You can even add exceptions for errors.

Thanks,
John
Comment 1 John Pierce 2016-06-13 18:24:06 UTC
Created attachment 33946 [details]
Example of Sampler HTTP Request Output (image)
Comment 2 Felix Schumacher 2016-06-13 18:56:04 UTC
So basically you want a flag to include/exclude samples from the result (tree/table) listeners?

I think it would be even better, if that decision could be delegated to a PostProcessor, which could add/clear a flag on the sample and the listener could then use that flag to decide, whether the sample should be displayed, or not.
Comment 3 Sebb 2016-06-13 23:29:32 UTC
(In reply to Felix Schumacher from comment #2)
> So basically you want a flag to include/exclude samples from the result
> (tree/table) listeners?
> 
> I think it would be even better, if that decision could be delegated to a
> PostProcessor, which could add/clear a flag on the sample and the listener
> could then use that flag to decide, whether the sample should be displayed,
> or not.

A Pre-Processor sounds more suitable to me.
Then the sampler need not store any data.
Comment 4 John Pierce 2016-06-14 09:25:06 UTC
> A Pre-Processor sounds more suitable to me.
> Then the sampler need not store any data.

Actually, I am using JSON Path in the GET Call (return Default Values) to capture the response message as a primer for the following Create HTTP Request.

So, I am temporarily saving at least 1 value.