On 29 August 2012 09:42, frank <[email protected]> wrote:
> i have a test plan like next :
>
> Test Plan
>      |__UDV
>      |
>      |__thread group 1
>      |       |
>      |       |__soap/xml-rpc request
>      |                |
>      |                |__xpath extractor
>      |
>      |__thread group 2
>                 |
>                 |__http request
>
> i want to define a variable 'test' in UDV, then i want to extract something
> from xml-rpc request and store the extraction result into the variable
> 'test' which defined in UDV, assume the extraction result is '123',
>
> then i want to use the extraction result '123' in thread group 2,
>
> i defined the 'reference name' is 'test' too in xpath extractor, but
> actually in thread group 2, the ${test} is not the extraction result,
>
> so how can i do?  or is there any other solution?

JMeter variables are local to a single thread, not just a thread group.
Variables defined in a UDV are made available to all threads, but
changes are applied locally.

It's not entirely clear why the http request has to be in a separate
thread group from the soap request.
I assume that the soap request is needed to extract some setup
information that is then used in subsequent requests.

If so, then it sounds like you need a setUp Thread Group for the soap request.
Store the info in a property (using the __setProperty function):

http://jmeter.apache.org/usermanual/functions.html#__setProperty

This can be referenced in other thread groups using the __P() function.

> Thanks in advance
>
>
>
>
> --
> View this message in context: 
> http://jmeter.512774.n5.nabble.com/use-extraction-result-in-other-thread-group-tp5714575.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> 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]

Reply via email to