jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pmoua...@apache.org
Subject svn commit: r1852921 - /jmeter/trunk/xdocs/usermanual/best-practices.xml
Date Mon, 04 Feb 2019 14:46:09 GMT
Author: pmouawad
Date: Mon Feb  4 14:46:09 2019
New Revision: 1852921

URL: http://svn.apache.org/viewvc?rev=1852921&view=rev
Log:
Fix typo

Thanks @ Ivan Ricanti

Modified:
    jmeter/trunk/xdocs/usermanual/best-practices.xml

Modified: jmeter/trunk/xdocs/usermanual/best-practices.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/best-practices.xml?rev=1852921&r1=1852920&r2=1852921&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/best-practices.xml (original)
+++ jmeter/trunk/xdocs/usermanual/best-practices.xml Mon Feb  4 14:46:09 2019
@@ -356,7 +356,7 @@ To run the test with 20 loops, just chan
 <p>
 This quickly becomes tedious if you want to run lots of tests in non-GUI mode.
 One solution to this is to define the Test Plan variable in terms of a property,
-for example <code>LOOPS=${__P(loops,10))}</code>.
+for example <code>LOOPS=${__P(loops,10)}</code>.
 This uses the value of the property "<code>loops</code>", defaulting to <code>10</code>
if the property is not found.
 The "<code>loops</code>" property can then be defined on the JMeter command-line:
 <source>jmeter &hellip; -Jloops=12 &hellip;</source>



Mime
View raw message