jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pmoua...@apache.org
Subject svn commit: r1806693 - /jmeter/trunk/xdocs/usermanual/component_reference.xml
Date Wed, 30 Aug 2017 12:59:36 GMT
Author: pmouawad
Date: Wed Aug 30 12:59:36 2017
New Revision: 1806693

URL: http://svn.apache.org/viewvc?rev=1806693&view=rev
Log:
Take Felix notes into account

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

Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1806693&r1=1806692&r2=1806693&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Wed Aug 30 12:59:36 2017
@@ -1682,7 +1682,7 @@ The current implementation supports stan
 includes extensions like <code>oneTimeSetUp</code> and <code>oneTimeTearDown</code>.
The sampler works like the
 <complink name="Java Request" /> with some differences.
 <ul>
-<li>rather than use Jmeter's test interface, it scans the jar files for classes extending
JUnit's <code>TestCase</code> class. That includes any class or subclass.</li>
+<li>rather than use JMeter's test interface, it scans the jar files for classes extending
JUnit's <code>TestCase</code> class. That includes any class or subclass.</li>
 <li>JUnit test jar files should be placed in <code>jmeter/lib/junit</code>
instead of <code>/lib</code> directory.
 You can also use the "<code>user.classpath</code>" property to specify where
to look for <code>TestCase</code> classes.</li>
 <li>JUnit sampler does not use name/value pairs for configuration like the <complink
name="Java Request" />. The sampler assumes <code>setUp</code> and <code>tearDown</code>
will configure the test correctly.</li>
@@ -1761,7 +1761,7 @@ The following JUnit4 annotations are rec
 <note>
 Note that JMeter currently runs the test methods directly, rather than leaving it to JUnit.
 This is to allow the <code>setUp</code>/<code>tearDown</code> methods
to be excluded from the sample time.
-As a consequence, the sampler time excludes the time taken to call setUp/tearDown methods.
+As a consequence, the sampler time excludes the time taken to call <code>setUp</code>/<code>tearDown</code>
methods and their annotation based alternatives.
 </note>
 </component>
 



Mime
View raw message