>Part of the confusion is caused by the fact that user defined variables
at
>the test plan level are visible to the entire plan, and the reference
is
>exactly the same ${varname} leading the first time users of JMeter to
think
>that any variable is global.
The docs specifically state that variables are local to threads. And
also say the first thing to do is add a threadgroup.. Not create
elements above the threadgroup :) Part of the issue is conceptualizing
'threads' being different instances with their own values because it can
be confusing on which data is reset/refreshed per thread while others
may be persistant.
The problem with the docs on variables is they are kind of spread out..
Being primarily referenced as an after thought in functions.
Docs need a concise summary table detailing usage of variables vs
properties (and difference between system and local properties). Items
of note are when they are processed, their scope, and possibilities to
define them (like command line vs UDV etc).
-----Original Message-----
From: Michael Giroux [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 5:13 PM
To: JMeter Users List
Subject: Re: How do you read and use values from a file?
> Variables are specifically designed to be local to threads (not just
> thread groups).
> This is because threads represent different users.
>
> JMeter properties are global, see:
>
> http://jakarta.apache.org/jmeter/usermanual/functions.html
It would be helpful to include little reminders such as this in the
documentation that creates variables. For example, the __javaScript
function reminds us to "Remember to include the necessary quotes ..."
It would be handy to remind us that the reference name created by a
function or element is local to the thread.
Part of the confusion is caused by the fact that user defined variables
at the test plan level are visible to the entire plan, and the reference
is exactly the same ${varname} leading the first time users of JMeter to
think that any variable is global.
---------------------------------------------------------------------
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]
