You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by se...@apache.org on 2007/07/03 21:36:52 UTC
svn commit: r552958 - in /jakarta/jmeter/branches/rel-2-2/xdocs: ./
usermanual/
Author: sebb
Date: Tue Jul 3 12:36:51 2007
New Revision: 552958
URL: http://svn.apache.org/viewvc?view=rev&rev=552958
Log:
Various document clarifications and tidyup
Modified:
jakarta/jmeter/branches/rel-2-2/xdocs/index.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/best-practices.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/boss.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-db-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ftp-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-point-to-point-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-topic-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldap-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldapext-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-monitor-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-web-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ws-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/get-started.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/intro.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/listeners.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/remote-test.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/test_plan.xml
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/index.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/index.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/index.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/index.xml Tue Jul 3 12:36:51 2007
@@ -57,11 +57,21 @@
<li>Several load statistics may be choosen with <b>pluggable timers</b>.</li>
<li>Data analysis and <b>visualization plugins</b> allow great extendibility
as well as personalization.</li>
- <li>Functions (which include JavaScript) can be used to provide dynamic input to a test</li>
- <li>Scriptable Samplers (BeanShell is supported in version 1.9.2 and above)</li>
+ <li>Functions can be used to provide dynamic input to a test or provide data manipulation.</li>
+ <li>Scriptable Samplers (BeanShell is fully supported; and there is a sampler which supports BSF-compatible languages)</li>
</ul>
</li>
</ul>
+<h2>JMeter is not a browser</h2>
+<p>
+JMeter is not a browser.
+As far as web-services and remote services are concerned, JMeter looks like a browser (or rather, multiple browsers);
+however JMeter does not perform all the actions supported by browsers.
+In particular, JMeter does not execute the Javascript found in HTML pages.
+Nor does it render the HTML pages as a browser does
+(it's possible to view the response as HTML etc, but the timings are not included in any samples, and only one sample in one thread is ever viewed at a time).
+</p>
+
<h2>How do I do it?</h2>
<ul>
<li><a href="usermanual/index.html">Using JMeter</a></li>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/best-practices.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/best-practices.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/best-practices.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/best-practices.xml Tue Jul 3 12:36:51 2007
@@ -132,6 +132,7 @@
<li>Don't use functional mode</li>
<li>Use CSV output rather than XML</li>
<li>Only save the data that you need</li>
+<li>Use as few Assertions as possible</li>
</ul>
</section>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/boss.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/boss.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/boss.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/boss.xml Tue Jul 3 12:36:51 2007
@@ -43,6 +43,7 @@
<p>Does our application have state ? If so, how does our application manage it
(cookies, session-rewriting, or some other method) ?
</p>
+<p>What is the testing intended to achieve?</p>
</subsection>
<subsection name="17.2 Resources">
<p>The following resources will prove very helpful. Bear in mind that if you
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-db-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-db-test-plan.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-db-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-db-test-plan.xml Tue Jul 3 12:36:51 2007
@@ -35,10 +35,9 @@
<complink name="JDBC Request"/>, <complink name="Graph Results"/>.</p>
<note>This example uses the MySQL database driver.
-To use this driver, its containing .jar file must be copied to the extension
-.../lib/ directory (see <a href="get-started.html#classpath">JMeter's Classpath</a>
-for more details). Otherwise, expect a substantial amount of stack traces when
-running this test plan.</note>
+To use this driver, its containing .jar file must be copied to the JMeter
+<b>lib</b> directory (see <a href="get-started.html#classpath">JMeter's Classpath</a>
+for more details).</note>
</section>
@@ -68,10 +67,10 @@
field, enter JDBC Users.</p>
<note>You will need a valid database, database table, and user-level access to that
-table. In the example shown here, the database is 'mydb' and the tables' name is
+table. In the example shown here, the database is 'mydb' and the table name is
'Stocks'.</note>
-<p>Next, increase the number of users (called threads) to 10.</p>
+<p>Next, increase the number of users to 10.</p>
<p>In the next field, the Ramp-Up Period, leave the the default value of 0
seconds. This property tells JMeter how long to delay between starting each
@@ -81,10 +80,9 @@
would be 1 second (5 users / 5 seconds = 1 user per second). If you set the
value to 0, then JMeter will immediately start all of your users.</p>
-<p>Finally, clear the checkbox labeled "Forever", and enter a value of 3 in
+<p>Finally, enter a value of 3 in
the Loop Count field. This property tells JMeter how many times to repeat your
-test. If you enter a loop count value of 0, then JMeter will run your test only
-once. To have JMeter repeatedly run your Test Plan, select the Forever
+test. To have JMeter repeatedly run your Test Plan, select the Forever
checkbox.</p>
<note>In most applications, you have to manually accept
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ftp-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ftp-test-plan.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ftp-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ftp-test-plan.xml Tue Jul 3 12:36:51 2007
@@ -67,7 +67,7 @@
<p>Start by providing a more descriptive name for our Thread Group. In the name
field, enter O'Reilly Users.</p>
-<p>Next, increase the number of users (called threads) to 4.</p>
+<p>Next, increase the number of users to 4.</p>
<p>In the next field, the Ramp-Up Period, leave the the default value of 0
seconds. This property tells JMeter how long to delay between starting each
@@ -77,10 +77,9 @@
would be 1 second (5 users / 5 seconds = 1 user per second). If you set the
value to 0, then JMeter will immediately start all of your users.</p>
-<p>Finally, clear the checkbox labeled "Forever", and enter a value of 2 in
+<p>Finally, enter a value of 2 in
the Loop Count field. This property tells JMeter how many times to repeat your
-test. If you enter a loop count value of 0, then JMeter will run your test only
-once. To have JMeter repeatedly run your Test Plan, select the Forever
+test. To have JMeter repeatedly run your Test Plan, select the Forever
checkbox.</p>
<note>In most applications, you have to manually accept
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-point-to-point-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-point-to-point-test-plan.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-point-to-point-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-point-to-point-test-plan.xml Tue Jul 3 12:36:51 2007
@@ -208,35 +208,8 @@
<section name="11.4 Saving the Test Plan" anchor="saving">
<p>Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
-File menu (with the latest release, it is no longer necessary to select the
-Test Plan element first).</p>
-
- <note>JMeter allows you to save the entire Test Plan tree or
-only a portion of it. To save only the elements located in a particular "branch"
-of the Test Plan tree, select the Test Plan element in the tree from which to start
-the "branch", and then click your right mouse button to access the Save As menu item.
-Alternatively, select the appropriate Test Plan element and then select Save As from
-the Edit menu.
- </note>
-
+File menu.</p>
</section>
- <section name="11.5 Running the Test Plan" anchor="running">
-
- <p>From the Run menu, select Run.</p>
-
- <note>JMeter lights up a green square in the upper-right-hand corner to indicate if a test is
-currently running. The square is turned gray when all tests stop. Even after you select "stop",
-the green light will stay on until all test threads have exited.</note>
-
- <p>Once JMeter has finished running your Test Plan, select Stop from the
-Run menu.</p>
- <p>If you selected a file to save the results to in your listener, then you will have a file that can be
-opened in any visualizer. Each visualizer will display the results in it's own fashion.</p>
-
- <note>It is possible to have the same file open in more than one visualizer. This is not a problem. JMeter
-will ensure during the test run that no sample is recorded to the same file more than once.</note>
-
- </section>
</body>
</document>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-topic-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-topic-test-plan.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-topic-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-topic-test-plan.xml Tue Jul 3 12:36:51 2007
@@ -194,32 +194,6 @@
file before running it. To save the Test Plan, select Save Test Plan from the
File menu.</p>
-<note>JMeter allows you to save the entire Test Plan tree or
-only a portion of it. To save only the elements located in a particular "branch"
-of the Test Plan tree, select the Test Plan element in the tree from which to start
-the "branch", and then click your right mouse button to access the Save As menu item.
-Alternatively, select the appropriate Test Plan element and then select Save As from
-the Edit menu.
-</note>
-
-</section>
-
-<section name="§-num;.5 Running the Test Plan" anchor="running">
-
-<p>From the Run menu, select Run.</p>
-
-<note>JMeter lights up a green square in the upper-right-hand corner to indicate if a test is
-currently running. The square is turned gray when all tests stop. Even after you select "stop",
-the green light will stay on until all test threads have exited.</note>
-
-<p>Once JMeter has finished running your Test Plan, select Stop from the
-Run menu.</p>
-<p>If you selected a file to save the results to in your listener, then you will have a file that can be
-opened in any visualizer. Each visualizer will display the results in it's own fashion.</p>
-
-<note>It is possible to have the same file open in more than one visualizer. This is not a problem. JMeter
-will ensure during the test run that no sample is recorded to the same file more than once.</note>
-
</section>
</body>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldap-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldap-test-plan.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldap-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldap-test-plan.xml Tue Jul 3 12:36:51 2007
@@ -145,29 +145,8 @@
<section name="9.6 Saving the Test Plan" anchor="saving">
<p>Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
- File menu (with the latest release, it is no longer necessary to select the
- Test Plan element first).</p>
-
- <note>JMeter allows you to save the entire Test Plan tree or
- only a portion of it. To save only the elements located in a particular "branch"
- of the Test Plan tree, select the Test Plan element in the tree from which to start
- the "branch", and then click your right mouse button to access the Save As menu item.
- Alternatively, select the appropriate Test Plan element and then select Save As from
- the Edit menu.
- </note>
-
+ File menu.</p>
</section>
-
-<section name="9.7 Running the Test Plan" anchor="running">
-
- <p>From the Run menu, select Run.</p>
-
- <note>JMeter lights up a green square in the upper-right-hand corner to indicate if a
- test is currently running. The square is turned gray when all tests stop. Even after
- you select "stop", the green light will stay on until all test threads have exited.</note>
-
-</section>
-
</body>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldapext-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldapext-test-plan.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldapext-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldapext-test-plan.xml Tue Jul 3 12:36:51 2007
@@ -54,7 +54,7 @@
<p>
Take care when using LDAP special characters in the distinghuished name, in that case (eg, you want to use a + sign in a
distinghuished name) you need to escape the character by adding an "\" sign before that character.
-extra exeption: if you want to add a \ character in a distinghuised name (in an add or rename operation), you need to use 4 backslashes.
+extra exeption: if you want to add a \ character in a distinguished name (in an add or rename operation), you need to use 4 backslashes.
examples:
cn=dolf\+smits to add/search an entry with the name like cn=dolf+smits
cn=dolf \\ smits to search an entry with the name cn=dolf \ smits
@@ -423,34 +423,6 @@
</ol>
</p>
</subsection>
-
-<subsection name="9b.5 Saving the Test Plan" anchor="save_test">
- <p>
-Although it is not required, we recommend that you save the Test Plan to a
- file before running it. To save the Test Plan, select Save Test Plan from the
- File menu (with the latest release, it is no longer necessary to select the
- Test Plan element first).
-</p>
- <p>JMeter allows you to save the entire Test Plan tree or
- only a portion of it. To save only the elements located in a particular "branch"
- of the Test Plan tree, select the Test Plan element in the tree from which to start
- the "branch", and then click your right mouse button to access the Save As menu item.
- Alternatively, select the appropriate Test Plan element and then select Save As from
- the Edit menu.
-</p>
-</subsection>
-
-<subsection name="9b.6 Running the Test Plan" anchor="run_test">
-<p>
-From the Run menu, select Run.
-</p>
-<p>
- JMeter lights up a green square in the upper-right-hand corner to indicate if a
- test is currently running. The square is turned gray when all tests stop. Even after
- you select "stop", the green light will stay on until all test threads have exited.
-</p>
-</subsection>
-
</section>
</body>
</document>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-monitor-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-monitor-test-plan.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-monitor-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-monitor-test-plan.xml Tue Jul 3 12:36:51 2007
@@ -154,34 +154,7 @@
<section name="§-num;.7 Saving the Test Plan" anchor="saving">
<p>Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
-File menu (with the latest release, it is no longer necessary to select the
-Test Plan element first).</p>
-
-<note>JMeter allows you to save the entire Test Plan tree or
-only a portion of it. To save only the elements located in a particular "branch"
-of the Test Plan tree, select the Test Plan element in the tree from which to start
-the "branch", and then click your right mouse button to access the Save As menu item.
-Alternatively, select the appropriate Test Plan element and then select Save As from
-the Edit menu.
-</note>
-
-</section>
-
-<section name="§-num;.8 Running the Test Plan" anchor="running">
-
-<p>From the Run menu, select Run.</p>
-
-<note>JMeter lights up a green square in the upper-right-hand corner to indicate if a test is
-currently running. The square is turned gray when all tests stop. Even after you select "stop",
-the green light will stay on until all test threads have exited.</note>
-
-<p>Once JMeter has finished running your Test Plan, select Stop from the
-Run menu.</p>
-<p>If you selected a file to save the results to in your listener, then you will have a file that can be
-opened in any visualizer. Each visualizer will display the results in it's own fashion.</p>
-
-<note>It is possible to have the same file open in more than one visualizer. This is not a problem. JMeter
-will ensure during the test run that no sample is recorded to the same file more than once.</note>
+File menu.</p>
</section>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-test-plan.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-test-plan.xml Tue Jul 3 12:36:51 2007
@@ -47,6 +47,7 @@
JMeter will save the element selected, plus all child elements beneath it. In this way,
you can save test tree fragments, individual elements, or the entire test plan.</p>
+<note>The workbench is not automatically saved with the test plan, but it can be saved separately as above.</note>
</subsection>
<subsection name="3.3 Configuring Tree Elements" anchor="config_element">
@@ -59,11 +60,18 @@
<subsection name="3.4 Running a Test Plan" anchor="run">
<p>To run your test plan, choose "start" from the "run" menu item. To stop your test
-plan, choose "stop" from the same menu. JMeter does not automatically give any
-indication of whether it is currently running. Some listeners make it obvious if
-JMeter is running, but the only way to be sure is to check the "run" menu. If "start"
-is disabled, and "stop" is enabled, JMeter is running your test plan (or, at least, it
-thinks it is).</p>
+plan, choose "stop" from the same menu.
+When JMeter is running, it shows a small green box at the right hand end of the section just under the menu bar.
+You can also check the "run" menu.
+If "start" is disabled, and "stop" is enabled,
+then JMeter is running your test plan (or, at least, it thinks it is).</p>
+<p>
+There are two types of stop command:
+<ul>
+<li>Stop (Control + '.') - stops the threads immediately</li>
+<li>Shutdown (Control + ',')- requests the threads to stop at the end of any current work</li>
+</ul>
+</p>
</subsection>
<subsection name="3.5 Scoping Rules" anchor="scoping_rules">
@@ -90,6 +98,18 @@
If more than one Manager is in the scope of a Sampler,
only one Manager is used, but there is currently no way to specify <b>which</b> is used.
</b>
+</subsection>
+<subsection name="3.6 Error reporting" anchor="error_reporting">
+<p>
+JMeter reports warnings and errors to the jmeter.log file, as well as some information on the test run itself.
+Just occaisionally there may be some errors that JMeter is unable to trap and log; these will appear on the command console.
+If a test is not behaving as you expect, please check the log file in case any errors have been reported (e.g. perhaps a syntax error in a function call).
+</p>
+<p>
+Sampling errors (e.g. HTTP 404 - file not found) are not normally reported in the log file.
+Instead these are stored as attributes of the sample result.
+The status of a sample result can be seen in the various different Listeners.
+</p>
</subsection>
</section>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-web-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-web-test-plan.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-web-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-web-test-plan.xml Tue Jul 3 12:36:51 2007
@@ -80,7 +80,7 @@
would be 1 second (5 users / 5 seconds = 1 user per second). If you set the
value to 0, then JMeter will immediately start all of your users.</p>
-<p>Finally, clear the checkbox labeled "Forever", and enter a value of 2 in
+<p>Finally enter a value of 2 in
the Loop Count field. This property tells JMeter how many times to repeat your
test. If you enter a loop count value of 1, then JMeter will run your test only
once. To have JMeter repeatedly run your Test Plan, select the Forever
@@ -100,12 +100,12 @@
</section>
<section name="5.2 Adding Default HTTP Request Properties" anchor="adding_defaults">
-<p>Now that we have defined our users, it is time define the tasks that they
+<p>Now that we have defined our users, it is time to define the tasks that they
will be performing. In this section, you will specify the default settings
for your HTTP requests. And then, in section 5.3, you will add HTTP Request
elements which use some of the default settings you specified here.</p>
-<p>Begin by selecting the Jakarta Users element. Click your right mouse button
+<p>Begin by selecting the Jakarta Users (Thread Group) element. Click your right mouse button
to get the Add menu, and then select Add --> Config Element --> HTTP Request
Defaults. Then, select this new element to view its Control Panel (see Figure 5.3).
</p>
@@ -204,8 +204,7 @@
<section name="5.6 Saving the Test Plan" anchor="saving">
<p>Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
-File menu (with the latest release, it is no longer necessary to select the
-Test Plan element first).</p>
+File menu.</p>
<note>JMeter allows you to save the entire Test Plan tree or
only a portion of it. To save only the elements located in a particular "branch"
@@ -225,13 +224,16 @@
currently running. The square is turned gray when all tests stop. Even after you select "stop",
the green light will stay on until all test threads have exited.</note>
-<p>Once JMeter has finished running your Test Plan, select Stop from the
+<p>The numbers to the left of the green square show the currently active and total number of threads.</p>
+
+<p>Once JMeter has finished running your Test Plan, the green box will turn to grey.
+If you wish to stop the test plan earlier, select Shutdown or Stop from the
Run menu.</p>
<p>If you selected a file to save the results to in your listener, then you will have a file that can be
-opened in any visualizer. Each visualizer will display the results in it's own fashion.</p>
+opened in any visualizer. Each visualizer will display the results in its own fashion.</p>
<note>It is possible to have the same file open in more than one visualizer. This is not a problem. JMeter
-will ensure during the test run that no sample is recorded to the same file more than once.</note>
+will ensure during the test run that no sample is recorded to the same file more than once (this only applies to XML format samples).</note>
</section>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ws-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ws-test-plan.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ws-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ws-test-plan.xml Tue Jul 3 12:36:51 2007
@@ -189,36 +189,10 @@
<section name="§-num;.4 Saving the Test Plan" anchor="saving">
<p>Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
-File menu (with the latest release, it is no longer necessary to select the
-Test Plan element first).</p>
-
-<note>JMeter allows you to save the entire Test Plan tree or
-only a portion of it. To save only the elements located in a particular "branch"
-of the Test Plan tree, select the Test Plan element in the tree from which to start
-the "branch", and then click your right mouse button to access the Save As menu item.
-Alternatively, select the appropriate Test Plan element and then select Save As from
-the Edit menu.
-</note>
+File menu.</p>
</section>
-<section name="§-num;.5 Running the Test Plan" anchor="running">
-
-<p>From the Run menu, select Run.</p>
-
-<note>JMeter lights up a green square in the upper-right-hand corner to indicate if a test is
-currently running. The square is turned gray when all tests stop. Even after you select "stop",
-the green light will stay on until all test threads have exited.</note>
-
-<p>Once JMeter has finished running your Test Plan, select Stop from the
-Run menu.</p>
-<p>If you selected a file to save the results to in your listener, then you will have a file that can be
-opened in any visualizer. Each visualizer will display the results in it's own fashion.</p>
-
-<note>It is possible to have the same file open in more than one visualizer. This is not a problem. JMeter
-will ensure during the test run that no sample is recorded to the same file more than once.</note>
-
-</section>
</body>
</document>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/component_reference.xml Tue Jul 3 12:36:51 2007
@@ -40,7 +40,11 @@
-->
<section name="§-num;.1 Samplers" anchor="samplers">
<description>
- <br>Samplers perform the actual work of JMeter.</br>
+ <p>
+ Samplers perform the actual work of JMeter.
+ Each sampler (except Test Action) generates one or more sample results.
+ The sample results have various attributes (success/fail, elapsed time, data size etc) and can be viewed in the various listeners.
+ </p>
</description>
<component name="FTP Request" index="§-num;.1.1" width="502" height="299" screenshot="ftptest/ftp-request.png">
<description>This controller lets you send an FTP "retrieve file" or "upload file" request to an FTP server.
@@ -103,7 +107,8 @@
<p>There are two versions of the sampler
- one uses the default Java HTTP implementation, the other uses Commons HttpClient.
- The default (Java) implementation has some limitations:</p>
+ </p>
+ <p>The default (Java) implementation has some limitations:</p>
<ul>
<li>There is no control over how connections are re-used.
When a connection is released by JMeter, it may or may not be re-used by the same thread.</li>
@@ -475,7 +480,7 @@
</component>
-<component name="LDAP Extended Request" index="§-num;.1.8" width="595" height="542" screenshot="ldapext_request.png">
+<component name="LDAP Extended Request" index="§-num;.1.8" width="594" height="309" screenshot="ldapext_request.png">
<description>This Sampler can send all 8 different LDAP request to an LDAP server. It is an extended version of the LDAP sampler,
therefore it is harder to configure, but can be made much closer resembling a real LDAP session.
<p>If you are going to send multiple requests to the same LDAP server, consider
@@ -757,9 +762,10 @@
<component name="BSF Sampler" index="§-num;.1.11" width="396" height="217" screenshot="bsfsampler.png">
-<note>This is Alpha code</note>
<description><p>This sampler allows you to write a sampler using a BSF scripting language.<br></br>
-
+ See the <a href="http://jakarta.apache.org/bsf/index.html">Apache Bean Scripting Framework</a>
+ website for details of the languages supported.
+ You may need to download the appropriate jars for the language; they should be put in the JMeter <b>lib</b> directory.
</p>
</description>
<properties>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/get-started.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/get-started.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/get-started.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/get-started.xml Tue Jul 3 12:36:51 2007
@@ -76,9 +76,6 @@
</note>
<p>Because JMeter uses only standard Java APIs, please do not file bug reports if your JRE fails to run
JMeter because of JRE implementation issues.</p>
-<note>
-Use the latest version of Java 1.4 or 1.5 for best results
-</note>
</subsection>
<subsection name="2.1.2 Operating Systems" anchor="os">
@@ -136,12 +133,12 @@
</subsection>
<subsection name="2.2.6 Apache SOAP" anchor="opt_soap">
-<p>Apache SOAP requires mail.jar and activation.jar. You need to download and copy these two jar files to your jmeter/lib directory. Once the files are in there, JMeter will automatically pick them up.</p>
+<p>Apache SOAP requires mail.jar and activation.jar. You need to download and copy these two jar files to your <b>jmeter/lib</b> directory. Once the files are in there, JMeter will automatically pick them up.</p>
</subsection>
<subsection name="2.2.7 BeanShell" anchor="opt_beanshell">
-<p>To run the BeanShell function or any of the BeanSell test elements (sampler, timer etc),
- you need to download the beanshell jar from <a href="http://www.beanshell.org/">http://www.beanshell.org/</a> and copy the jar file to the jmeter/lib directory, where JMeter will automatically pick it up.</p>
+<p>To run the BeanShell function or any of the BeanShell test elements (sampler, timer etc),
+ you need to download the beanshell jar from <a href="http://www.beanshell.org/">http://www.beanshell.org/</a> and copy the jar file to the <b>jmeter/lib directory</b>, where JMeter will automatically pick it up.</p>
</subsection>
<subsection name="2.2.7 Libraries for ActiveMQ 3.0" anchor="libraries_activemq">
@@ -406,7 +403,7 @@
</property>
</properties>
<p><b>
-See also the comments in the jmeter.properties file for further information on other settings you can change.
+See also the comments in the jmeter.properties, user.properties and system.properties files for further information on other settings you can change.
</b></p>
</section>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/intro.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/intro.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/intro.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/intro.xml Tue Jul 3 12:36:51 2007
@@ -39,7 +39,7 @@
results you expect. For maximum flexibility, JMeter lets you create these assertions using
regular expressions.</p>
-
+<p>But please note that JMeter is not a browser.</p>
<subsection name="1.1 History" anchor="history">
<p>Stefano Mazzocchi of the Apache Software Foundation was the original developer of JMeter.
He wrote it primarily to test the performance of Apache JServ (a project that has
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/listeners.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/listeners.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/listeners.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/listeners.xml Tue Jul 3 12:36:51 2007
@@ -72,21 +72,16 @@
The configuration of this listener is controlled by entries in the file jmeter.properties.
</p>
<p>
-This feature can be used to specify a different data log file for each test run, for example:
-<code>
-jmeter -n -t testplan.jmx -l testplan_01.jtl
-jmeter -n -t testplan.jmx -l testplan_02.jtl
-</code>
+This feature can be used to specify different data and log files for each test run, for example:
+<pre>
+jmeter -n -t testplan.jmx -l testplan_01.jtl -j testplan_01.log
+jmeter -n -t testplan.jmx -l testplan_02.jtl -j testplan_02.log
+</pre>
</p>
<p>
-However, note that jmeter logging messages are written to jmeter.log by default.
+Note that jmeter logging messages are written to the jmeter.log by default.
This file is recreated each time, so if you want to keep the log files for each run,
-you will need to rename it after the run has finished.
-Or you can use the environment variable JVM_ARGS to pass in the option -Dlog_file=filename.
-This will define the Java system property,
-which will be used as the default JMeter property if not overridden in jmeter.properties
-If you are using an OS such as VMS just use a logical name for the log file in jmeter.properties
-and define the logical before starting JMeter.
+you will need to rename it using the -j option as above. The -j option was added in version 2.3.
</p>
</section>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/remote-test.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/remote-test.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/remote-test.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/remote-test.xml Tue Jul 3 12:36:51 2007
@@ -38,7 +38,9 @@
<li>Managment of multiple JMeterEngines from a single machine </li>
</ul>
</p>
-
+<p>
+However, remote mode does use more resources than running the same number of non-GUI tests independently.
+</p>
<p>Note that while you can indeed execute the JMeterEngine on your application
server, you need to be mindful of the fact that this will be adding processing
overhead on the application server and thus your testing results will be
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/test_plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/test_plan.xml?view=diff&rev=552958&r1=552957&r2=552958
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/test_plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/test_plan.xml Tue Jul 3 12:36:51 2007
@@ -25,7 +25,7 @@
<section name="4. Elements of a Test Plan">
-<p>The Test Plan object has a new checkbox to select called "Functional Testing". If selected, it
+<p>The Test Plan object has a checkbox called "Functional Testing". If selected, it
will cause JMeter to record the data returned from the server for each sample. If you have
selected a file in your test listeners, this data will be written to file. This can be useful if
you are doing a small run to ensure that JMeter is configured correctly, and that your server
@@ -33,6 +33,7 @@
JMeter's performance will suffer. This option should be off if you are doing stress-testing (it
is off by default). </p>
<p>If you are not recording the data to file, this option makes no difference.</p>
+<p>You can also use the Configuration button on a listener to decide what fields to save.</p>
<subsection name="4.1 ThreadGroup" anchor="thread_group">
<p>Thread group elements are the beginning points of any test plan. All elements
@@ -218,8 +219,12 @@
Other listeners provide summary or aggregation information.
</p>
-<p>Additionally, listeners can direct the data they collect to a file for later use. Every
-listener in JMeter provides a field to indicate the file to store data to.</p>
+<p>
+Additionally, listeners can direct the data to a file for later use.
+Every listener in JMeter provides a field to indicate the file to store data to.
+There is also a Configuration button which can be used to choose which fields to save, and whether to use CSV or XML format.
+<b>Note that all Listeners save the same data; the only difference is in the way the data is presented on the screen.</b>
+</p>
<p>Listeners can be added anywhere in the test. They will collect data only from elements at or
below their level. </p>
@@ -235,7 +240,7 @@
your Thread Group. If you do not add a delay, JMeter could overwhelm your server by
making too many requests in a very short amount of time.</p>
-<p>The timer will cause JMeter to delay a certain amount of time between each
+<p>The timer will cause JMeter to delay a certain amount of time before each
request that a thread makes.</p>
<p>
@@ -259,7 +264,10 @@
will then check that the text is present in the HTTP response. If JMeter cannot find the
text, then it will mark this as a failed request.</p>
-<p>To view the assertion results, add an Assertion Listener to the Thread Group.</p>
+<p>To view the assertion results, add an Assertion Listener to the Thread Group.
+Failed Assertions will also show up in the Tree View and Table Listeners,
+and will count towards the error %age for example in the Aggregate and Summary reports.
+</p>
</subsection>
<subsection name="4.6 Configuration Elements" anchor="config_elements">
@@ -289,13 +297,54 @@
<subsection name="4.9 Execution order" anchor="executionorder">
<ol>
-<li>Timers - if any</li>
+<li>Pre-Processors</li>
+<li>Timers</li>
<li>Sampler</li>
<li>Post-Processors (unless SampleResult is null)</li>
<li>Assertions (unless SampleResult is null)</li>
<li>Listeners (unless SampleResult is null)</li>
</ol>
+<note>
+Please note that Timers, Assertions, Pre- and Post-Processors are only processed if there is a sampler to which they apply.
+Logic Controllers and Samplers are processed in the order in which they appear in the tree.
+Other test elements are processed according to the scope in which they are found, and the type of test element.
+[Within a type, elements are processed in the order in which they appear in the tree].
+</note>
+<p>
+For example, in the following test plan:
+<ul>
+<li>Controller</li>
+<ul>
+<li>Post-Processor 1</li>
+<li>Sampler 1</li>
+<li>Sampler 2</li>
+<li>Timer 1</li>
+<li>Assertion 1</li>
+<li>Pre-Processor 1</li>
+<li>Timer 2</li>
+<li>Post-Processor 2</li>
+</ul>
+</ul>
+The order of execution would be:
+<pre>
+Pre-Processor 1
+Timer 1
+Timer 2
+Sampler 1
+Post-Processor 1
+Post-Processor 2
+Assertion 1
+
+Pre-Processor 1
+Timer 1
+Timer 2
+Sampler 2
+Post-Processor 1
+Post-Processor 2
+Assertion 1
+</pre>
+</p>
</subsection>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org