OK so with a simple test structure it works. This is my bad...
Thanks for the reply.
I had created a number of callable collections of different operations , and
had placed them under a disabled loop control, trying to create a "library of
reusable operations so to speak"
I had a another enabled loop control where I was calling these collections
using a Module controller
It seems as though the variable gets lost doing it this way and becomes a
literal hence I see in the results tree; LDAP Extended Request ${TNO}
This is some sort of scope issue and I think I will just take a simpler route
for now. As if I don't have the Library and define/run everything inside the
main loop it displays just fine.
Thanks again
Andy
-----Original Message-----
From: Deepak Shetty [mailto:[email protected]]
Sent: Friday, December 11, 2009 1:10 PM
To: JMeter Users List
Subject: Re: View results in tree displaying variable
works fine for me(Jmeter 2.3.4)
Thread Group
+BeanShell Sampler (sets up variable x to have value y) LDAP Extended
+Request ${x) View results tree
Value displays as LDAP Extended Request y.
Whats your test structure? can you simplify to just the basic values and see?
regards
deepak
On Thu, Dec 10, 2009 at 3:15 PM, Yourn, Andrew <[email protected]> wrote:
> New user implementing a LDAP functional regression suite :
>
> Trying without luck to get a variable to display in the view results
> in a tree sampler, specifically the left hand pane of the sampler
> where I observe the samplers that run. For example :
>
> If I have a sampler say "LDAP extended Request" and in the Name field
> on this sampler I put LDAP test ${TESTNO_somevar}
>
> All I ever see in the view results tree sampler is "LDAP test" even
> though I know through say the debug sampler that ${TESTNO_somevar} has
> a value in it.
>
> Any assistance with this would be appreciated...
>
>
>
> ---------------------------------------------------------------------
> 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]
