>-----Original Message----- >From: Boylan, Crispin [mailto:[EMAIL PROTECTED] >Sent: 26 February 2004 15:26 >To: 'JMeter Developers List' >Subject: RE: Current Status Of JMeter Nightlies > > >ok i'll file that one.
Thanks > >i've also noticed something else - its related to the >behaviour of timers in >the scripts, is it correct to have the following > >HTTP Request >Timer n >HTTP Request > >in order to get 2 http request separated by a gap of n seconds or > >HTTP Request > | > -> Timer n (child of HTTP Request) >HTTP Request > >as in the latest nightlies, the first scenario seems to be ignored and >treates as: > >Timer n >HTTP Request >HTTP Request > >Up to now i've been assuming that the order of commands in the list is >strictly followed by JMeter (except for things like Random containers) > The test tree is not followed in strict order - although samplers and controllers are executed in the specified order, some other elements are not. For example, you can place listeners anywhere at a given level, including before any samplers, and they will see all the sample results in that level - and below. Timers behave similarly. Quote from one of Mike Stover's postings: "You can attach a timer at any point in the test tree. If you attach it to the threadgroup, it will apply to every sampler within the threadgroup. If you attach it just to the first sample, it will only delay the first sample." If necessary, you can always add a Simple Controller to the test plan. S. ___________________________________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ___________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
