I like all of your suggestions! Automatically grouping "sets" using a simple controller for each one would be a fantistic step forward. I currently have to record each set as a separate group manually so this would be a terrific boon.
Automatically saving the samples as children of a controller also makes the Test Plan clearer for adding other components such as Interleave controllers and looping. One of my current problems is identifying the first sample in a set (for the purpose of adding a timer). This would make it so much easier for us to add timers to the first or last child manually. If it would be easy to perform this automatically, why then even better! Thank you for spending the time to ponder my particular problem. Paul > from: Jordi Salvat i Alabart <[EMAIL PROTECTED]> > date: Wed, 26 Nov 2003 16:00:15 > to: [EMAIL PROTECTED] > subject: Re: Handling timers in recorded scripts > > Yes, just having the proxy generate a timer for each request would > resolve Paul's issue. > > -- > Salut, > > Jordi. > > En/na BAZLEY, Sebastian ha escrit: > > This is a follow-up to the discussion on frames and problems with placing > > timers. > > > > Not sure if this would help, but the code in CVS has an option for the proxy > > recorder to generate separators - when there is a sufficient pause between > > samples, the recorder can output a dummy simple controller to separate the > > sets of samples. Further, the recorder can automatically add a response > > assertion to the first sample in a set (it assumes that this contains the > > main information from the response). > > > > There may be other ways of detecting all the browser requests that > > correspond to the original "click" by the user (e.g. perhaps the browser > > keeps the connection open for all the requests associated with a particular > > click?). > > > > Either way, let's assume that we can detect the boundaries between sets of > > samples. > > > > Would it be useful to generate a simple controller for each set (i.e. each > > user click), and save the samples as children of that? I think this would be > > reasonably simple to do (as an option). > > > > One could have further options to add other child elements to each > > controller group, e.g. always add a timer. > > > > In the case of a timer the value could even be derived from the detected > > pause (particularly if the browaer uses a single connection for each sample > > set). > > > > S. > > > > --------------------------------------------------------------------- > > 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]
