jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pmoua...@apache.org
Subject svn commit: r1854709 - in /jmeter/trunk/xdocs: changes.xml usermanual/component_reference.xml
Date Sun, 03 Mar 2019 13:31:56 GMT
Author: pmouawad
Date: Sun Mar  3 13:31:55 2019
New Revision: 1854709

URL: http://svn.apache.org/viewvc?rev=1854709&view=rev
Log:
Bug 62446 - Counter documentation is wrong in required fieds
Bugzilla Id: 62446

Modified:
    jmeter/trunk/xdocs/changes.xml
    jmeter/trunk/xdocs/usermanual/component_reference.xml

Modified: jmeter/trunk/xdocs/changes.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/changes.xml?rev=1854709&r1=1854708&r2=1854709&view=diff
==============================================================================
--- jmeter/trunk/xdocs/changes.xml [utf-8] (original)
+++ jmeter/trunk/xdocs/changes.xml [utf-8] Sun Mar  3 13:31:55 2019
@@ -147,6 +147,7 @@ Summary
 
 <h3>Timers, Assertions, Config, Pre- &amp; Post-Processors</h3>
 <ul>
+    <li><bug>62446</bug>Counter documentation is wrong in required fieds.
Contributed by orimarko at gmail.com</li>
 </ul>
 
 <h3>Functions</h3>
@@ -183,6 +184,7 @@ Summary
     <li>Benoit Vatan (benoit.vatan at gmail.com)</li>
     <li>Graham Russell (graham at ham1.co.uk)</li>
     <li>Brian Wolfe (wolfebrian2120 at gmail.com)</li>
+    <li>orimarko at gmail.com</li>
 </ul>
 <p>We also thank bug reporters who helped us improve JMeter.</p>
 <ul>

Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1854709&r1=1854708&r2=1854709&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Sun Mar  3 13:31:55 2019
@@ -4243,10 +4243,10 @@ with the start, continuing on like that
 </description>
 <properties>
         <property name="Name" required="">Descriptive name for this element that is
shown in the tree.</property>
-        <property name="Starting value" required="Yes">The starting value for the counter.
 The counter will equal this
-        value during the first iteration.</property>
+        <property name="Starting value" required="No">The starting value for the counter.
 The counter will equal this
+        value during the first iteration (defaults to 0).</property>
         <property name="Increment" required="Yes">How much to increment the counter
by after each
-        iteration.</property>
+        iteration (defaults to 0, meaning no increment).</property>
         <property name="Maximum value" required="No">If the counter exceeds the maximum,
then it is reset to the <code>Starting value</code>.
         Default is <code>Long.MAX_VALUE</code>
         </property>
@@ -4255,9 +4255,9 @@ with the start, continuing on like that
         If there is a problem interpreting the format, then it is ignored.
     [The default format is generated using <code>Long.toString()</code>]
         </property>
-        <property name="Exported Variable Name" required="Yes">This will be the variable
name under which the counter value is available.  
+        <property name="Exported Variable Name" required="No">This will be the variable
name under which the counter value is available.  
         If you name it <code>counterA</code>, you can then access it using <code>${counterA}</code>

-        as explained in <a href="functions.html">user-defined values</a></property>
+        as explained in <a href="functions.html">user-defined values</a> (By
default, it creates an empty string variable that can be accessed using <code>${}</code>
but this is highly discouraged)</property>
         <property name="Track Counter Independently for each User" required="No">In
other words, is this a global counter, or does each user get their
         own counter?  If unchecked, the counter is global (i.e., user #1 will get value "<code>1</code>",
and user #2 will get value "<code>2</code>" on
         the first iteration).  If checked, each user has an independent counter.</property>



Mime
View raw message