woolfel 2004/10/11 11:56:26
Modified: xdocs/usermanual Tag: rel-2_0 functions.xml
Log:
fixed the index numbers for functions
peter
Revision Changes Path
No revision
No revision
1.14.2.11 +21 -21 jakarta-jmeter/xdocs/usermanual/functions.xml
Index: functions.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/functions.xml,v
retrieving revision 1.14.2.10
retrieving revision 1.14.2.11
diff -u -r1.14.2.10 -r1.14.2.11
--- functions.xml 11 Oct 2004 18:35:52 -0000 1.14.2.10
+++ functions.xml 11 Oct 2004 18:56:26 -0000 1.14.2.11
@@ -22,7 +22,7 @@
<body>
-<section name="16. Functions" anchor="functions">
+<section name="17. Functions" anchor="functions">
<p>
JMeter functions are special values that can populate fields of any Sampler or
other configuration
element in a test tree. A function looks like this:</p>
@@ -52,7 +52,7 @@
<li><a href="#__split">split - Split a string into variables</a></li>
</ul>
-<subsection name="16.1 What can functions do" anchor="what_can_do">
+<subsection name="17.1 What can functions do" anchor="what_can_do">
<p>There are two kinds of functions: user-defined static values, and built-in
functions.<br/>
User-defined static values allow the user to define variables to be replaced with
their static value when
a test tree is compiled and submitted to be run. This replacement happens once at
the beginning of the test
@@ -68,7 +68,7 @@
request throughout the course of the test. </p>
</subsection>
-<subsection name="16.2 Where can functions be used?" anchor="where">
+<subsection name="17.2 Where can functions be used?" anchor="where">
<p>A user-defined function can be written into any field of any test component.
Some fields do not allow random strings
because they are expecting numbers, and thus will not accept a function. However,
most fields will allow
functions.</p>
@@ -76,7 +76,7 @@
Samplers, Timers, Listeners, Modifiers, Assertions, Pre-Processors, Post-Processors
and Config Elements.</p>
</subsection>
-<subsection name="16.3 Writing the function string" anchor="how">
+<subsection name="17.3 Writing the function string" anchor="how">
<p>User-defined functions take the form: <code>${varName}</code>. In the TestPlan
tree element, a two-column table
of user-defined values is kept, matching up variable names with static values.
Referencing the
variable in a test element is done by bracketing the variable name with '${' and
'}'.</p>
@@ -90,7 +90,7 @@
variable will override the built-in function.</note>
</subsection>
-<subsection name="16.4 The Function Helper Dialog" anchor="function_helper">
+<subsection name="17.4 The Function Helper Dialog" anchor="function_helper">
<p>The Function Helper dialog is available from JMeter's Tools menu.</p>
<figure image="function_helper_dialog.png">Function Helper Dialog</figure>
<p>Using the Function Helper, you can select a function from the pull down, and
assign
@@ -101,9 +101,9 @@
for you to copy-paste into your test plan wherever you like.</p>
</subsection>
-<subsection name="16.5 Functions" anchor="functions">
+<subsection name="17.5 Functions" anchor="functions">
-<component index="16.5.1" name="__regexFunction">
+<component index="17.5.1" name="__regexFunction">
<description><p>The Regex Function is used to parse the previous response using any
regular
expression (provided by user). The function returns the template string with
variable values filled
in.</p>
@@ -152,7 +152,7 @@
</properties>
</component>
-<component index="16.5.2" name="__counter">
+<component index="17.5.2" name="__counter">
<description><p>The counter generates a new number each time it is called, starting
with 1
and incrementing by +1 each time. The counter can be configured to keep each
simulated user's values
separate, or to use the same counter for all user. If each user's values is
incremented separately,
@@ -169,7 +169,7 @@
</properties>
</component>
-<component index="16.5.3" name="__threadNum">
+<component index="17.5.3" name="__threadNum">
<description><p>The thread number function simply returns the number of the thread
currently
being executed. These numbers are independent of ThreadGroup, meaning thread #1 in
one threadgroup
is indistinguishable from thread #1 in another threadgroup, from the point of view
of this function.</p>
@@ -178,7 +178,7 @@
</description>
</component>
-<component index="16.5.4" name="__intSum">
+<component index="17.5.4" name="__intSum">
<description><p>The intsum function can be used to compute the sum of two or more
integer values.
</p></description>
@@ -193,7 +193,7 @@
<!-- Alternate spelling -->
<a name="__StringFromFile"/>
-<component index="16.5.5" name="_StringFromFile">
+<component index="17.5.5" name="_StringFromFile">
<description>
<p>
@@ -265,7 +265,7 @@
</p>
</component>
-<component index="16.5.6" name="__machineName">
+<component index="17.5.6" name="__machineName">
<description><p>The machineName function returns the local host
name</p></description>
<properties>
@@ -274,7 +274,7 @@
</properties>
</component>
-<component index="16.5.7" name="__javaScript">
+<component index="17.5.7" name="__javaScript">
<description><p>The javaScript function executes a piece of JavaScript (not Java!)
code and returns its value</p>
</description>
@@ -293,7 +293,7 @@
</properties>
</component>
-<component index="16.5.8" name="__Random">
+<component index="17.5.8" name="__Random">
<description><p>The random function returns a random number that lies between the
given min and max values.</p></description>
<properties>
@@ -304,7 +304,7 @@
</properties>
</component>
-<component index="16.5.8" name="__CSVRead">
+<component index="17.5.8" name="__CSVRead">
<description><p>The CSVFile function returns a string from a CSV file (c.f. <a
href="#_StringFromFile">StringFromFile</a>)</p>
<p>NOTE: versions up to 1.9.1 only supported a single file.
JMeter versions since 1.9.1 support multiple file names.
@@ -341,7 +341,7 @@
</properties>
</component>
-<component index="16.5.9" name="__property">
+<component index="17.5.9" name="__property">
<description><p>The property function returns the value of a JMeter property.
If the property value cannot be found, and no default has been supplied, it
returns the property name.
When supplying a default value, there is no need to provide a function name -
the parameter can be set to null, and it will be ignored.
@@ -363,7 +363,7 @@
</properties>
</component>
-<component index="16.5.10" name="__P">
+<component index="17.5.10" name="__P">
<description><p>This is a simplified property function which is
intended for use with properties defined on the command line.
Unlike the __property function, there is no option to save the value in a
variable,
@@ -399,7 +399,7 @@
</properties>
</component>
-<component index="16.5.11" name="__log">
+<component index="17.5.11" name="__log">
<description>
<p>
The log function logs a message, and returns its input string
@@ -416,7 +416,7 @@
</p>
</component>
-<component index="16.5.12" name="__logn">
+<component index="17.5.12" name="__logn">
<description>
<p>
The logn function logs a message, and returns the empty string
@@ -433,7 +433,7 @@
</p>
</component>
-<component index="16.5.13" name="__BeanShell">
+<component index="17.5.13" name="__BeanShell">
<description>
<p>
The BeanShell function evaluates the script passed to it, and returns the
result.
@@ -482,7 +482,7 @@
</p>
</component>
-<component index="16.5.14" name="__split">
+<component index="17.5.14" name="__split">
<description>
<p>
The split function splits the string passed to it according to the delimiter,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
