Hello.

Thanks (Mike) for the pointer on how to 're'reference the values of named counters in 
a test plan. Works!

I am having trouble similar trouble properly using the last (ie name) argument of the 
__regexFunction.

Looking at a substructure I have in my Test Plan:

Assume preceding structure produces a preceding HTTP response
Simple Controller
  HTTP Request Defaults (uses two __regexFunction(...,name)s
                         param: oneName,
                         value: ${__regexFunction(...,oneREF)}
                         param: twoName,
                         value: ${__regexFunction(...,twoREF)} )
  HTTP Request ONE      (param: oneName, value: ${oneREF}
                         param: twoName, value: ${twoREF} )
  HTTP Request TWO      (param: oneName, value: ${oneREF}
                         param: twoName, value: ${twoREF} )

So, I was hoping to get the HTTP Requests, ONE and TWO, to visit their Paths with the 
same parameter name,value pairs.

The ${oneREF} and ${twoREF} do not expand. They are literaly repeated in the generated 
request URLs (yep, I am using GET).

Also, though the parameter names used in the HTTP Request Defaults is the same as 
those in the individual requests, the parameters oneName and twoName appear twice in 
the generated URLs of both HTTP Requests ONE and TWO. The default values and the 
request specified values are both used to generate the URLs.

Separated by '&' I get this parameter list on each HTTP Request:

oneName=${oneREF}
twoName=${twoREF}
oneName=org.apache.jmeter.functions.CompoundFunction@86793e
twoName=org.apache.jmeter.functions.CompoundFunction@81f91a

As you can see the ${__regexFunction(...,name)} invocations are expanded (in the HTTP 
Request Defaults) to the default Object.toString() values of an underlying Java object 
in the test plan execution.

Thanks for any pointers. I hope this is simple misuse on my part.
John Kavadias    [EMAIL PROTECTED]


Reply via email to