Thanks. -----Original Message----- From: Michael Stover [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 03, 2005 12:29 PM To: [email protected] Subject: Re: Scoping rules and behavior of Constant Timer
It's doing what it's supposed to, but delays come before their target samplers... -Mike On Tue, 2005-05-03 at 11:49 -0700, Scott Pack wrote: > What is the expected behavior of the Constant Timer as a child of a Sampler > (HTTP for example)? The documentation states that this component is 'strictly > hierarchical', however what I find is not consistent with this statement. > Here is the script: > > Test Plan > --->Thread Group 1 > ---->---->Loop Controller (5 iterations) > ---->---->---->HTTP Request 1.1 > ---->---->---->---->Constant Timer (10000) > ---->---->---->HTTP Request 1.2 > ---->---->---->HTTP Request 1.3 > > Actual: Every ten seconds, requests 1.1 - 1.3 are issued sequentially without > delay between requests, i.e. 1.1 -> 1.2 -> 1.3 -> sleep 10sec -> 1.1 -> 1.2 > -> 1.3 -> sleep 10sec... > Expected: 10 second delay after request 1.1, no delay between other requests, > i.e. 1.1 -> sleep 10sec -> 1.2 -> 1.3 -> 1.1 -> sleep 10 sec... > > Thus it appears there is no way to set a timer for an individual sampler that > needs extra time (such as submitting form data...) within a loop controller. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
