You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jmeter.apache.org by mi...@apache.org on 2013/07/24 11:03:22 UTC
svn commit: r1506446 - in /jmeter/trunk:
docs/images/screenshots/template_menu.png
docs/images/screenshots/template_wizard.png
xdocs/images/screenshots/template_menu.png
xdocs/images/screenshots/template_wizard.png xdocs/usermanual/get-started.xml
Author: milamber
Date: Wed Jul 24 09:03:22 2013
New Revision: 1506446
URL: http://svn.apache.org/r1506446
Log:
Update get started page. Update Templates... screenshots
Modified:
jmeter/trunk/docs/images/screenshots/template_menu.png
jmeter/trunk/docs/images/screenshots/template_wizard.png
jmeter/trunk/xdocs/images/screenshots/template_menu.png
jmeter/trunk/xdocs/images/screenshots/template_wizard.png
jmeter/trunk/xdocs/usermanual/get-started.xml
Modified: jmeter/trunk/docs/images/screenshots/template_menu.png
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/images/screenshots/template_menu.png?rev=1506446&r1=1506445&r2=1506446&view=diff
==============================================================================
Binary files - no diff available.
Modified: jmeter/trunk/docs/images/screenshots/template_wizard.png
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/images/screenshots/template_wizard.png?rev=1506446&r1=1506445&r2=1506446&view=diff
==============================================================================
Binary files - no diff available.
Modified: jmeter/trunk/xdocs/images/screenshots/template_menu.png
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/images/screenshots/template_menu.png?rev=1506446&r1=1506445&r2=1506446&view=diff
==============================================================================
Binary files - no diff available.
Modified: jmeter/trunk/xdocs/images/screenshots/template_wizard.png
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/images/screenshots/template_wizard.png?rev=1506446&r1=1506445&r2=1506446&view=diff
==============================================================================
Binary files - no diff available.
Modified: jmeter/trunk/xdocs/usermanual/get-started.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/get-started.xml?rev=1506446&r1=1506445&r2=1506446&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/get-started.xml (original)
+++ jmeter/trunk/xdocs/usermanual/get-started.xml Wed Jul 24 09:03:22 2013
@@ -31,7 +31,7 @@
<p>The easiest way to begin using JMeter is to first
<a href="http://jmeter.apache.org/download_jmeter.cgi">download the latest production release</a> and install it.
The release contains all of the files you need to build and run most types of tests,
-e.g. Web (HTTP/HTTPS), FTP, JDBC, LDAP, Java, and JUnit.</p>
+e.g. Web (HTTP/HTTPS), FTP, JDBC, LDAP, Java, JUnit and more.</p>
<p>If you want to perform JDBC testing,
then you will, of course, need the appropriate JDBC driver from your vendor. JMeter does not come with
any JDBC drivers.</p>
@@ -64,12 +64,12 @@ various configuration elements (timers,
over your Test Plans.</p>
<subsection name="§-num;.0.1 Create Test Plan from Template" anchor="template">
-<p>Starting with version 2.10, you have the ability to create a new Test Plan from existing template.</p>
-<p>To do so you use menu item "New from templates":
-<figure image="template_menu.png">New from Templates menu item</figure>
+<p>You have the ability to create a new Test Plan from existing template.</p>
+<p>To do so you use the menu <b>File</b> > <b>Templates...</b> or Templates icon:
+<figure image="template_menu.png">Templates icon item</figure>
</p>
<p>A popup appears, you can then choose a template among the list:
-<figure image="template_wizard.png">Templates wizard</figure>
+<figure image="template_wizard.png">Templates popup</figure>
</p>
<p>A documentation for each template explains what to do once test plan is created from template.</p>
</subsection>
@@ -113,7 +113,7 @@ implementation.</p>
<subsection name="§-num;.2.3 Email Support" anchor="opt_email">
<p>JMeter has extensive Email capabilities.
It can send email based on test results, and has a POP3(S)/IMAP(S) sampler.
-It also has an SMTP sampler.
+It also has an SMTP(S) sampler.
</p>
</subsection>
@@ -125,14 +125,14 @@ Include the necessary encryption package
Also, update <a href="#configuring_jmeter">system.properties</a> to register the SSL Provider.</p>
<p>
JMeter HTTP defaults to protocol level TLS. This can be changed by editting the JMeter property
-"https.default.protocol" in jmeter.properties or user.properties.
+<i>https.default.protocol</i> in jmeter.properties or user.properties.
</p>
<p><b>The JMeter HTTP samplers are configured to accept all certificates,
-whether trusted or not, regardless of validity periods etc.</b>
+whether trusted or not, regardless of validity periods, etc.</b>
This is to allow the maximum flexibility in testing servers.</p>
<p>If the server requires a client certificate, this can be provided.</p>
<p>There is also the <complink name="SSL Manager"/>, for greater control of certificates.</p>
-<note>The JMeter proxy server (see below) supports recording HTTPS (SSL) in versions after 2.3.4</note>
+<note>The JMeter proxy server (see below) supports recording HTTPS (SSL)</note>
<p>
The SMTP sampler can optionally use a local trust store or trust all certificates.
</p>
@@ -184,18 +184,19 @@ and the JAVA_HOME environment variable s
Note: there can be problems (especially with client-server mode) if the directory path contains any spaces.
</p>
<p>
-The installation directory structure should look something like this (for version 2.7):
+The installation directory structure should look something like this (where X.Y is version number):
<pre>
-apache-jmeter-2.7
-apache-jmeter-2.7/bin
-apache-jmeter-2.7/docs
-apache-jmeter-2.7/extras
-apache-jmeter-2.7/lib/
-apache-jmeter-2.7/lib/ext
-apache-jmeter-2.7/lib/junit
-apache-jmeter-2.7/printable_docs
+apache-jmeter-X.Y
+apache-jmeter-X.Y/bin
+apache-jmeter-X.Y/docs
+apache-jmeter-X.Y/extras
+apache-jmeter-X.Y/lib/
+apache-jmeter-X.Y/lib/ext
+apache-jmeter-X.Y/lib/junit
+apache-jmeter-X.Y/licenses
+apache-jmeter-X.Y/printable_docs
</pre>
-You can rename the parent directory (i.e. apache-jmeter-2.7) if you want, but do not change any of the sub-directory names.
+You can rename the parent directory (i.e. apache-jmeter-X.Y) if you want, but do not change any of the sub-directory names.
</p>
</section>
@@ -203,7 +204,7 @@ You can rename the parent directory (i.e
<br/>
<p>To run JMeter, run the jmeter.bat (for Windows) or jmeter (for Unix) file.
These files are found in the bin directory.
-After a short pause, the JMeter GUI should appear.
+After a short time, the JMeter GUI should appear.
</p>
<p>
@@ -272,7 +273,7 @@ Do not use lib/ext for utility jars; it
Other jars (such as JDBC, JMS implementations and any other support libaries needed by the JMeter code)
should be placed in the <b>lib</b> directory - not the <b>lib/ext</b> directory</p>
<p>Note: JMeter will only find .jar files, not .zip.</p>
-<p>You can also install utility Jar files in $JAVA_HOME/jre/lib/ext, or (since 2.1.1) you can set the property <b>user.classpath</b> in jmeter.properties</p>
+<p>You can also install utility Jar files in $JAVA_HOME/jre/lib/ext, or you can set the property <b>user.classpath</b> in jmeter.properties</p>
<p>Note that setting the CLASSPATH environment variable will have no effect.
This is because JMeter is started with "java -jar",
and the java command silently ignores the CLASSPATH variable, and the -classpath/-cp options when -jar is used.
@@ -281,7 +282,7 @@ and the java command silently ignores th
<subsection name="§-num;.4.2 Using a Proxy Server" anchor="proxy_server">
<p>If you are testing from behind a firewall/proxy server, you may need to provide JMeter with
-the firewall/proxy server hostname and port number. To do so, run the jmeter.bat/jmeter file
+the firewall/proxy server hostname and port number. To do so, run the jmeter[.bat] file
from a command line with the following parameters:</p>
<p>
-H [proxy server hostname or ip address]<br/>
@@ -299,16 +300,20 @@ This is not to be confused with the prox
<subsection name="§-num;.4.3 Non-GUI Mode (Command Line mode)" anchor="non_gui">
<p>For non-interactive testing, you may choose to run JMeter without the GUI. To do so, use
-the following command options</p>
-<p>-n This specifies JMeter is to run in non-gui mode</p>
-<p>-t [name of JMX file that contains the Test Plan].</p>
-<p>-l [name of JTL file to log sample results to].</p>
-<p>-j [name of JMeter run log file].</p>
-<p>-r Run the test in the servers specified by the JMeter property "remote_hosts"</p>
-<p>-R [list of remote servers] Run the test in the specified remote servers</p>
+the following command options:</p>
+<p>
+-n This specifies JMeter is to run in non-gui mode<br/>
+-t [name of JMX file that contains the Test Plan].<br/>
+-l [name of JTL file to log sample results to].<br/>
+-j [name of JMeter run log file].<br/>
+-r Run the test in the servers specified by the JMeter property "remote_hosts"<br/>
+-R [list of remote servers] Run the test in the specified remote servers
+</p>
<p>The script also lets you specify the optional firewall/proxy server information:</p>
-<p>-H [proxy server hostname or ip address]<br/>
--P [proxy server port]</p>
+<p>
+-H [proxy server hostname or ip address]<br/>
+-P [proxy server port]
+</p>
<p><b>Example</b>: jmeter -n -t my_test.jmx -l log.jtl -H my.proxy.server -P 8000</p>
<p>
If the property <code>jmeterengine.stopfail.system.exit</code> is set to true (default is false),
@@ -320,7 +325,7 @@ Normally this is not necessary.
<subsection name="§-num;.4.4 Server Mode" anchor="server">
<p>For <a href="remote-test.html">distributed testing</a>, run JMeter in server mode on the remote node(s), and then control the server(s) from the GUI.
You can also use non-GUI mode to run remote tests.
-To start the server(s), run jmeter-server/jmeter-server.bat on each server host.</p>
+To start the server(s), run jmeter-server[.bat] on each server host.</p>
<p>The script also lets you specify the optional firewall/proxy server information:</p>
<p>-H [proxy server hostname or ip address]<br/>
-P [proxy server port]</p>
@@ -346,11 +351,13 @@ Normally this is not necessary.
<subsection name="§-num;.4.5 Overriding Properties Via The Command Line" anchor="override">
<p>Java system properties, JMeter properties, and logging properties can be overriden directly on the command line (instead of modifying jmeter.properties).
To do so, use the following options:</p>
-<p>-D[prop_name]=[value] - defines a java system property value.</p>
-<p>-J[prop name]=[value] - defines a local JMeter property.</p>
-<p>-G[prop name]=[value] - defines a JMeter property to be sent to all remote servers.</p>
-<p>-G[propertyfile] - defines a file containing JMeter properties to be sent to all remote servers.</p>
-<p>-L[category]=[priority] - overrides a logging setting, setting a particular category to the given priority level.</p>
+<p>
+-D[prop_name]=[value] - defines a java system property value.<br/>
+-J[prop name]=[value] - defines a local JMeter property.<br/>
+-G[prop name]=[value] - defines a JMeter property to be sent to all remote servers.<br/>
+-G[propertyfile] - defines a file containing JMeter properties to be sent to all remote servers.<br/>
+-L[category]=[priority] - overrides a logging setting, setting a particular category to the given priority level.
+</p>
<p>The -L flag can also be used without the category name to set the root logging level.</p>
<p><b>Examples</b>:
<pre>
@@ -376,15 +383,15 @@ jmeter -LDEBUG</pre>
It defaults to <b>jmeter.log</b>, and will be found in the directory from which JMeter was launched.
</p>
<p>
- Since JMeter 2.6, menu <b>Options > Log Viewer</b> displays the log file in a bottom pane on main JMeter window.
+ The menu <b>Options > Log Viewer</b> displays the log file in a bottom pane on main JMeter window.
</p>
<p>
- Since JMeter 2.7 (GUI mode), the number of error/fatal messages logged in the log file is displayed at top-right.
+ In the GUI mode, the number of error/fatal messages logged in the log file is displayed at top-right.
</p>
<figure image="log_errors_counter.png">Error/fatal counter</figure>
<p>
- JMeter versions after 2.2 added a new command-line option, -j jmeterlogfile.
- This is processed after the initial properties file is read,
+ The command-line option <i>-j jmeterlogfile</i> allow to process
+ after the initial properties file is read,
and before any further properties are processed.
It therefore allows the default of jmeter.log to be overridden.
The jmeter scripts that take a test plan name as a parameter (e.g. jmeter-n.cmd) have been updated
@@ -498,7 +505,7 @@ If set to 0, then JMeter does not start
your own copy of the jmeter.properties and specify it in the command line.
</p>
<note>
- Note: since 2.2, you can define additional JMeter properties in the file defined by the
+ Note: You can define additional JMeter properties in the file defined by the
JMeter property <b>user.properties</b> which has the default value <b>user.properties</b>.
The file will be automatically loaded if it is found in the current directory
or if it is found in the JMeter bin directory.