If you do implement this, I think it might be easy to do as a pre-processor. That way it can add the params from the context vars before the request is sent.
So a RegEx post-processor would collect the vars, and then the pre-processor would plug em into the next request. I don't *need* this now, because my app is only going to have 10 rows max, so I can just build it to handle up to 10 rows statically. Otherwise, I'd build the pre-processor now. I bet it wouldn't be too hard. Rob > If it's any consolation, I'd be hard put to come up with a more useful > single improvement to JMeter right at this moment. What that means is > that, if my current employer ever requires me to do serious work with > JMeter, I'll probably implement it. :-) > > -Mike > > On Wed, 2005-06-15 at 13:45 -0400, Rob Butler wrote: >> YES! Darn.. >> >> Thanks. >> >> > If I understand you right, you need a foreach construct within the >> HTTP >> > Sampler's argument list. That would be a very useful thing, I think, >> > but right now, JMeter doesn't do anything like that. >> > >> > -Mike >> > >> > On Wed, 2005-06-15 at 13:04 -0400, Rob Butler wrote: >> >> Yes, I have. My understanding of the ForEach controller is that it >> will >> >> execute a separate HTTP Request sample for each entry in a RegEx >> list. >> >> That will not do what I need. I need to submit *one* request that >> >> contains all the name/value pairs that I collected. Is there an >> >> alternate >> >> means of using the ForEach controller to do that? >> >> >> >> If so, could you explain in detail how to use the ForEach controller >> in >> >> that manner, because the docs and wiki samples I have read were not >> >> clear >> >> at all on doing that. >> >> >> >> Thanks again! >> >> Rob >> >> >> >> > Have you looked at the ForEach Controller? >> >> > >> >> > http://jakarta.apache.org/jmeter/usermanual/component_reference.html#ForEach_Controller >> >> > >> >> > S. >> >> > On 6/15/05, Rob Butler <[EMAIL PROTECTED]> wrote: >> >> >> Hello all, >> >> >> >> >> >> I am attempting to perf test a web app with jmeter, but I don't >> know >> >> how >> >> >> to solve a particular issue I am running into. >> >> >> >> >> >> One particular page in the app can return a dynamic number of rows >> of >> >> >> data. The number of rows is dependent upon the individual user's >> >> >> information in a DB. There is no way of knowing ahead of time how >> >> many >> >> >> rows there are. >> >> >> >> >> >> What I would like to do is capture (using regex's) the form data >> that >> >> is >> >> >> returned in the response, and use that as the parameters to the >> next >> >> >> request. >> >> >> >> >> >> Using the Regular Expression Extractor I can easily get all the >> data >> >> and >> >> >> field names as a list of capture groups. The problem is, how do I >> >> then >> >> >> dynamically build the parameters that will be used in the next >> >> request? >> >> >> In the HTTP Request sampler I can put a field name, and use a >> dynamic >> >> >> value, but that won't do what I need. I need to use dynamic field >> >> names >> >> >> and dynamic values in the request. Is this possible? How do I do >> >> it? >> >> >> >> >> >> Thanks >> >> >> Rob >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> 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] >> > >> > >> > >> > --------------------------------------------------------------------- >> > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
