Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jmeter.apache.org
Received-SPF: pass (athena.apache.org: domain of apc4@ya.ru designates
 84.201.143.141 as permitted sender)
Message-ID: <552E302E.5040304@ya.ru>
Date: Wed, 15 Apr 2015 12:32:30 +0300
From: Andrey Pokhilko <apc4@ya.ru>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: dev@jmeter.apache.org
Subject: Post-Sampler Timers
Content-Type: multipart/alternative;
 boundary="------------020801090006020704030303"

--------------020801090006020704030303
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi,

When I try to introduce JMeter to new people, I frequently see them
confused with our way to set "think times" before request. Especially
those who used to use some other testing tools, where think-time is
_after_ request.

I personally think that think-time should be made after request, because
its duration depends on the results of the request. If you have got long
text as a result of your request, you supposed to spend some time
reading it. If you have short error message, you supposed to do your
next request much faster. The _delay_ time before request still makes
sense, because it allows manipulating throughput and synchronize requests.

I would like to contribute to JMeter following changes:

 1. Add a property for Timers, marking them as "pre-sampler" or
    "post-sampler" timers
 2. Modify thread execution flow to call pre-timers and post-timers
    accordingly
 3. Modify timers UIs where it is reasonable, adding radio button to
    change timer mode


Any thoughts/objections on this?

-- 
Andrey Pokhilko


--------------020801090006020704030303--