The scoping will stay the same. The implementation will be pretty straightforward and I don't see any complications, just couple of "if" statements.
Andrey Pokhilko On 04/15/2015 12:37 PM, UBIK LOAD PACK Support 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 <a...@ya.ru> 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 >> >> >
