Well, that's just my own feedback / opinion. It doesn't reflect others. If the new implementation feels right, I'll adopt it, I just cannot see the benefit of that, yet. Neither I don't see the issue with having "Think Time" elements between actions, such as: http://pasteboard.co/2BDxVS03.png What do you mean by "...which makes test plan too heavy." ?
Shmuel Krakower. www.Beatsoo.org - re-use your jmeter scripts for application performance monitoring from worldwide locations for free. On Wed, Apr 15, 2015 at 4:19 PM, Andrey Pokhilko <[email protected]> wrote: > But the sampler approach (test action is also a sampler) requires to > have a pause element after each sampler, which makes test plan too > heavy. Timers have scoping, this allows lean test-plan building. That's > why I want to have post-sample timers. > > Andrey Pokhilko > > On 04/15/2015 03:12 PM, Shmuel Krakower wrote: > > Hi, > > I do exactly as ubikloadpack mentioned which makes things a lot easier to > > look at. > > I don't see much value with pre_sleep and post_sleep. > > It would have been nice to have a "sleep sampler", which will reduce the > > need to create TestAction with Timer in it, as done today. > > > > Best, > > > > > > > > Shmuel Krakower. > > www.Beatsoo.org - re-use your jmeter scripts for application performance > > monitoring from worldwide locations for free. > > > > On Wed, Apr 15, 2015 at 12:37 PM, UBIK LOAD PACK Support < > > [email protected]> wrote: > > > >> Hi, > >> Very good idea ! > >> We always use the following strategy to have this feature: > >> > >> - Use TestAction with 0 sleep and nest in it the Timer. This way > timer > >> pauses where it is located for the expected time and not > SampleResult is > >> generated. > >> > >> So you idea would help as it is a bit harder to maintain. > >> One note although, how would you handle scoping ? > >> Would it stay as is ? If yes, won't code be difficult and clumsy ? > >> > >> Regards > >> @ubikloadpack > >> > >> On Wed, Apr 15, 2015 at 11:32 AM, Andrey Pokhilko <[email protected]> wrote: > >> > >>> 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 > >>> > >>> > >> > >> -- > >> > >> Regards > >> Ubik Load Pack <http://ubikloadpack.com> Team > >> Follow us on Twitter <http://twitter.com/ubikloadpack> > >> > >> > >> Cordialement > >> L'équipe Ubik Load Pack <http://ubikloadpack.com> > >> Suivez-nous sur Twitter <http://twitter.com/ubikloadpack> > >> > >
