jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fschumac...@apache.org
Subject svn commit: r1717846 - in /jmeter/trunk/xdocs/usermanual: build-ldap-test-plan.xml component_reference.xml get-started.xml
Date Thu, 03 Dec 2015 20:54:41 GMT
Author: fschumacher
Date: Thu Dec  3 20:54:41 2015
New Revision: 1717846

URL: http://svn.apache.org/viewvc?rev=1717846&view=rev
Log:
Markup changes. Usage of the newly add menu-tags and the older code and note tags.

Modified:
    jmeter/trunk/xdocs/usermanual/build-ldap-test-plan.xml
    jmeter/trunk/xdocs/usermanual/component_reference.xml
    jmeter/trunk/xdocs/usermanual/get-started.xml

Modified: jmeter/trunk/xdocs/usermanual/build-ldap-test-plan.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/build-ldap-test-plan.xml?rev=1717846&r1=1717845&r2=1717846&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/build-ldap-test-plan.xml (original)
+++ jmeter/trunk/xdocs/usermanual/build-ldap-test-plan.xml Thu Dec  3 20:54:41 2015
@@ -19,7 +19,6 @@
 <!DOCTYPE document
 [
 <!ENTITY sect-num '9a'>
-<!ENTITY rarr     "&#x02192;" >
 ]>
 
 <document prev="build-ftp-test-plan.html" next="build-ldapext-test-plan.html" id="$Id$">
@@ -47,7 +46,11 @@ repeat 4 times) = 40 LDAP requests. To c
 The Thread Group tells JMeter the number of users you want to simulate, how often the users
should send
 requests, and the how many requests  they should send.</p>
                 <p>Go ahead and add the ThreadGroup element by first selecting the
Test Plan, clicking your
-right mouse button to get the <b>Add</b> menu, and then select <b>Add</b>&rarr;<b>ThreadGroup</b>.
You should now see the
+right mouse button to get the <menuchoice><guimenuitem>Add</guimenuitem></menuchoice>
menu, and then select
+<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>ThreadGroup</guimenuitem>
+</menuchoice>. You should now see the
 Thread Group element under Test Plan. If you do not see the element, then "expand" the Test
Plan tree by
 clicking on the Test Plan element.
 <figure image="ldaptest/threadgroup.png">
@@ -56,10 +59,15 @@ Figure &sect-num;.1. Thread Group and fi
 </p>
 </section>
     <section name="&sect-num;.2 Adding Login Config Element" anchor="add_login">
-        <p>Begin by selecting the <b>LDAP Users</b> element. Click your
right mouse
-button to get the Add menu, and then select <b>Add</b>&rarr;<b>Config
Element</b>&rarr;<b>Login Config Element</b>.
+        <p>Begin by selecting the <code>LDAP Users</code> element. Click
your right mouse
+button to get the Add menu, and then select
+  <menuchoice>
+    <guimenuitem>Add</guimenuitem>
+    <guimenuitem>Config Element</guimenuitem>
+    <guimenuitem>Login Config Element</guimenuitem>
+  </menuchoice>.
 Then,  select this new element to view its Control Panel.</p>
-        <p>Like most JMeter elements, the <b>Login  Config Element</b>'s
Control Panel has a name
+        <p>Like most JMeter elements, the <code>Login  Config Element</code>'s
Control Panel has a name
 field that you can modify. In this example, leave this field with the default value.</p>
 
 <figure image="ldaptest/login-config-element.png">
@@ -72,19 +80,24 @@ field that you can modify. In this examp
 </section>
 
     <section name="&sect-num;.3 Adding LDAP Request Defaults" anchor="add_defaults">
-                <p>Begin by selecting the LDAP Users element. Click your right mouse
button
-to get the <b>Add</b> menu, and then select <b>Add</b>&rarr;<b>Config
Element</b>&rarr;<b>LDAP Request Defaults</b>. Then,
+                <p>Begin by selecting the <code>LDAP Users</code> element.
Click your right mouse button
+to get the <menuchoice><guimenuitem>Add</guimenuitem></menuchoice>
menu, and then select
+<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Config Element</guimenuitem>
+  <guimenuitem>LDAP Request Defaults</guimenuitem>
+</menuchoice>. Then,
 select this new element to view its Control Panel.</p>
-        <p>Like most JMeter elements, the <b>LDAP Request Defaults</b>
Control Panel has a name
+        <p>Like most JMeter elements, the <code>LDAP Request Defaults</code>
Control Panel has a name
 field that you can modify. In this example, leave this field with the default value.</p>
 
 
 <figure image="ldaptest/requestdefaults.png">
   Figure &sect-num;.3 LDAP Defaults for our Test Plan</figure>
 
-        <note>Enter DN field to "your LDAP Root Distinguished Name".<br/>
-                Enter LDAP Server's Servername field to "ldap.test.com".<br/>
-        The port to 389.<br/>
+        <note>Enter <code>DN</code> field to "<code>your LDAP Root
Distinguished Name</code>".<br/>
+                Enter LDAP Server's <code>Servername</code> field to "<code>ldap.test.com</code>".<br/>
+        The <code>port</code> to <code>389</code>.<br/>
         These values are default for the LDAP Requests.</note>
 </section>
 
@@ -99,33 +112,37 @@ field that you can modify. In this examp
 
         </ol>
         <p>JMeter sends requests in the order that you add them to the tree.
-Start by adding the first LDAP Request to the LDAP Users element (<b>Add</b>&rarr;<b>
-Sampler</b>&rarr;<b>LDAP Request</b>). Then, select the LDAP Request
 element in the tree
+Start by adding the first LDAP Request to the LDAP Users element
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Sampler</guimenuitem>
+  <guimenuitem>LDAP Request</guimenuitem>
+</menuchoice>). Then, select the LDAP Request  element in the tree
 and edit the following properties</p>
         <ol>
-            <li>Rename to "Add" this element</li>
-            <li>Select the <b>Add Test</b> radio button in <b>Test
Configuration</b> group</li>
+            <li>Rename to "<code>Add</code>" this element</li>
+            <li>Select the <code>Add Test</code> radio button in <code>Test
Configuration</code> group</li>
         </ol>
                 <figure image="ldaptest/add.png">
                   Figure &sect-num;.4.1 LDAP Request for Inbuilt Add test</figure>
 
 
-                <p>You do not have to set the Server Name field, port field, Username,
Password
-and DN because you already specified this value in the <b>Login Config Element</b>
and
-<b>LDAP Request Defaults.</b></p>
+                <p>You do not have to set the <code>Servername</code> field,
<code>port</code> field, <code>Username</code>, <code>Password</code>
+and <code>DN</code> because you already specified this value in the <code>Login
Config Element</code> and
+<code>LDAP Request Defaults.</code></p>
         <p>Next, add the second LDAP Request and edit the following
 properties</p>
         <ol>
-            <li>Rename to "Search" this element</li>
-            <li>Select the <b>Search Test</b> radio button in <b>Test
Configuration</b> group</li>
+            <li>Rename to "<code>Search</code>" this element</li>
+            <li>Select the <code>Search Test</code> radio button in <code>Test
Configuration</code> group</li>
         </ol>
         Next, add the Third LDAP Request and edit the following properties
                 <figure image="ldaptest/search.png">
                   Figure &sect-num;.4.2 LDAP Request for Inbuilt Search test</figure>
 
         <ol>
-            <li>Rename to "Modify" this element</li>
-            <li>Select the <b>Modify Test</b> radio button in <b>Test
Configuration</b> group</li>
+            <li>Rename to "<code>Modify</code>" this element</li>
+            <li>Select the <code>Modify Test</code> radio button in <code>Test
Configuration</code> group</li>
         </ol>
         Next, add the fourth LDAP Request and edit the following properties
                 
@@ -133,8 +150,8 @@ properties</p>
                   Figure &sect-num;.4.3 LDAP Request for Inbuilt Modify test</figure>
 
         <ol>
-            <li>Rename to "Delete" this element</li>
-            <li>Select the <b>Delete Test</b> radio button in <b>Test
Configuration</b> group</li>
+            <li>Rename to "<code>Delete</code>" this element</li>
+            <li>Select the <code>Delete Test</code> radio button in <code>Test
Configuration</code> group</li>
         </ol>
                 <figure image="ldaptest/delete.png">
                   Figure &sect-num;.4.4 LDAP Request for Inbuilt Delete test</figure>
@@ -142,13 +159,18 @@ properties</p>
 </section>
 <section name="&sect-num;.5 Adding a Response Assertion" anchor="ResponseAssertion">
                <p>You can add a Response Assertion element.
- This element will check the received response data by verifying if the response text is
"successful".
-  (<b>Add</b>&rarr;<b>Assertion</b>&rarr;<b>Response
Assertion</b>).<br>Note: A this position in the tree,
-  the Response Assertion will be executed for each LDAP Request.</br></p>
+ This element will check the received response data by verifying if the response text is
"<code>successful</code>".
+  (<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Assertion</guimenuitem>
+  <guimenuitem>Response Assertion</guimenuitem>
+</menuchoice>).</p>
+<note>Note: A this position in the tree,
+  the Response Assertion will be executed for each LDAP Request.</note>
           <ol>
-            <li>Select <b>Text Response</b> Radio button in <b>Response
Field to Test</b> group</li>
-            <li>Select <b>Substring</b> Radio button in <b>Pattern
Matching Rules</b> group</li>
-            <li>Click on <b>Add</b> button and add the string "successful"
in <b>Pattern to Test</b> field</li>
+            <li>Select <code>Text Response</code> Radio button in <code>Response
Field to Test</code> group</li>
+            <li>Select <code>Substring</code> Radio button in <code>Pattern
Matching Rules</code> group</li>
+            <li>Click on <code>Add</code> button and add the string "<code>successful</code>"
in <code>Pattern to Test</code> field</li>
         </ol>
 <figure image="ldaptest/responseassertion.png">
   Figure &sect-num;.5 LDAP Response Assertion</figure>
@@ -157,7 +179,12 @@ properties</p>
                <p>The final element you need to add to your Test Plan is a Listener.
  This element is responsible for storing all of the results of your LDAP
 requests in a file  and presenting a visual model of the data. Select the LDAP
-Users element and add a View Results in Table (<b>Add</b>&rarr;<b>Listener</b>&rarr;<b>View
Results in Table</b>)</p>
+Users element and add a View Results in Table
+(<menuchoice>
+<guimenuitem>Add</guimenuitem>
+<guimenuitem>Listener</guimenuitem>
+<guimenuitem>View Results in Table</guimenuitem>
+</menuchoice>)</p>
 <figure image="ldaptest/viewtable.png">
   Figure &sect-num;.6 View Results in Table Listener</figure>
 

Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1717846&r1=1717845&r2=1717846&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Thu Dec  3 20:54:41 2015
@@ -20,7 +20,6 @@
 [
 <!ENTITY sect-num '19'>
 <!ENTITY hellip   "&#x02026;" >
-<!ENTITY rarr     "&#x02192;" >
 <!ENTITY le       "&#x02264;" >
 <!ENTITY ge       "&#x02265;" >
 ]>
@@ -731,9 +730,9 @@ See <a href="build-ws-test-plan.html">Bu
  (true). If you need to maintain the session, add a blank Header Manager. The
  sampler uses the Header Manager to store the SOAPHTTPConnection object, since
  the version of apache soap does not provide a easy way to get and set the cookies.</p>
- <p><b>Note:</b> If you are using CSVDataSet, do not check "Memory Cache".
If memory
+ <note>If you are using CSVDataSet, do not check "Memory Cache". If memory
  cache is checked, it will not iterate to the next value. That means all the requests
- will use the first value.</p>
+ will use the first value.</note>
  <p>Make sure you use <code>&lt;soap:Envelope</code> rather than <code>&lt;Envelope</code>.
For example:</p>
  <source>
 &lt;?xml version="1.0" encoding="utf-8"?&gt;
@@ -1216,7 +1215,7 @@ return "Data from sample with Label "+La
 SampleResult.setResponseData("My data");
 return null;
 </source>
-<p>Another example:<br></br> ensure that the property <b>beanshell.sampler.init=BeanShellSampler.bshrc</b>
is defined in <code>jmeter.properties</code>. 
+<p>Another example:<br></br> ensure that the property <code>beanshell.sampler.init=BeanShellSampler.bshrc</code>
is defined in <code>jmeter.properties</code>. 
 The following script will show the values of all the variables in the <code>ResponseData</code>
field:
 </p>
 <source>
@@ -2951,10 +2950,9 @@ Match[9]=#__counter
 (Word, Excel, PowerPoint 97-2003, 2007-2010 (openxml), Apache OpenOffice (writer, calc, impress),
HTML,
 gzip, jar/zip files (list of content), and some meta-data on "multimedia" files like mp3,
mp4, flv, etc. The complete list of 
 support format is available on <a href="http://tika.apache.org/1.2/formats.html">Apache
Tika format page.</a>
-<br/><br/>
-<b>Note:</b> A requirement to the <code>Document view</code> is to
download the <a href="http://tika.apache.org/download.html">
+<note>A requirement to the <code>Document view</code> is to download the
<a href="http://tika.apache.org/download.html">
 Apache Tika binary package</a> (<code>tika-app-x.x.jar</code>) and put
this in <code>JMETER_HOME/lib</code> directory.
-<br/><br/>
+</note>
 If the document is larger than 10 MB, then it won't be displayed.
 To change this limit, set the JMeter property <code>document.max_size</code>
(unit is byte) or set to <code>0</code> to remove the limit.
 <br/></td></tr>
@@ -4117,8 +4115,8 @@ instead. (see figures 12 and 13).</p>
         <property name="Variable Name" required="Yes">The name of the variable the
connection is tied to.  
         Multiple connections can be used, each tied to a different variable, allowing JDBC
Samplers
         to select the appropriate connection.
-        <b>Each name must be different. If there are two configuration elements using
the same name,
-        only one will be saved. JMeter versions after 2.3 log a message if a duplicate name
is detected.</b>
+        <note>Each name must be different. If there are two configuration elements
using the same name,
+        only one will be saved. JMeter versions after 2.3 log a message if a duplicate name
is detected.</note>
         </property>
         <property name="Max Number of Connections" required="Yes">
         Maximum number of connections allowed in the pool.
@@ -4149,7 +4147,7 @@ The Database URL and JDBC Driver class a
 <p>Some possible settings are shown below. Please check the exact details in the JDBC
driver documentation.</p>
 
 <p>
-If JMeter reports <b>No suitable driver</b>, then this could mean either:
+If JMeter reports <code>No suitable driver</code>, then this could mean either:
 </p>
 <ul>
 <li>The driver class was not found. In this case, there will be a log message such
as <code>DataSourceElement: Could not load driver: {classname} java.lang.ClassNotFoundException:
{classname}</code></li>
@@ -4251,9 +4249,9 @@ To make JMeter use more than one certifi
 
 <component name="User Defined Variables" index="&sect-num;.4.16"  width="741" height="266"
screenshot="user_defined_variables.png">
 <description><p>The User Defined Variables element lets you define an <b>initial
set of variables</b>, just as in the <complink name="Test Plan" />.
-<b>
+<note>
 Note that all the UDV elements in a test plan - no matter where they are - are processed
at the start.
-</b>
+</note>
 So you cannot reference variables which are defined as part of a test run, e.g. in a Post-Processor.
 </p>
 <p>
@@ -6147,7 +6145,7 @@ Such variables should be used for items
 but which remain the same during a test run.
 </p>
 <p>
-<b>Note that the Test Plan cannot refer to variables it defines.</b> 
+<note>Note that the Test Plan cannot refer to variables it defines.</note> 
 If you need to construct other variables from the Test Plan variables, 
 use a <complink name="User Defined Variables"/> test element.
 </p>
@@ -6270,7 +6268,8 @@ Your WorkBench can be saved independentl
   JDK).
 </p>
 <p>
-  To select the client certificate, choose <code>Options</code>&rarr;<code>SSL
Manager</code> from the menu bar.
+  To select the client certificate, choose <menuchoice><guimenuitem>Options</guimenuitem>
+  <guimenuitem>SSL Manager</guimenuitem></menuchoice> from the menu bar.
   You will be presented with a file finder that looks for PKCS12 files by default.
   Your PKCS12 file must have the extension '<code>.p12</code>' for SSL Manager
to recognize it
   as a PKCS12 file.  Any other file will be treated like an average JKS key store.
@@ -6311,7 +6310,13 @@ Ensure you read this <a href="https://wi
 
 <p>To use the recorder, <i>add</i> the HTTP(S) Test Script Recorder element
to the workbench.
 Select the WorkBench element in the tree, and right-click on this element to get the
-Add menu (<code>Add</code> &rarr; <code>Non-Test Elements</code>
&rarr; <code>HTTP(S) Test Script Recorder</code>).</p>
+Add menu 
+(<menuchoice>
+  <guimenuitem>Add</guimenuitem>
+  <guimenuitem>Non-Test Elements</guimenuitem>
+  <guimenuitem>HTTP(S) Test Script Recorder</guimenuitem>
+</menuchoice>
+).</p>
 <p>
 The recorder is implemented as an HTTP(S) proxy server.
 You need to set up your browser use the proxy for all HTTP and HTTPS requests.
@@ -6355,7 +6360,7 @@ This should be defined in the file <code
 </p>
 <p>
 The JMeter certificates are generated (if necessary) when the <code>Start</code>
button is pressed.
-<b>Certificate generation can take some while, during which time the GUI will be unresponsive.</b>
+<note>Certificate generation can take some while, during which time the GUI will be
unresponsive.</note>
 The cursor is changed to an hour-glass whilst this is happening.
 When certificate generation is complete, the GUI will display a pop-up dialogue containing
the details of the certificate for the root CA.
 This certificate needs to be installed by the browser in order for it to accept the host
certificates generated by JMeter; see <a href="#install_cert">below</a> for details.

Modified: jmeter/trunk/xdocs/usermanual/get-started.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/get-started.xml?rev=1717846&r1=1717845&r2=1717846&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/get-started.xml (original)
+++ jmeter/trunk/xdocs/usermanual/get-started.xml Thu Dec  3 20:54:41 2015
@@ -19,7 +19,6 @@
 <!DOCTYPE document[
 <!ENTITY sect-num '2'>
 <!ENTITY hellip   "&#x02026;" >
-<!ENTITY rarr     "&#x02192;" >
 ]>
 
 <document prev="intro.html" next="build-test-plan.html" id="$Id$">
@@ -422,7 +421,8 @@ jmeter -Duser.dir=/home/mstover/jmeter_s
         It defaults to <code>jmeter.log</code>, and will be found in the directory
from which JMeter was launched.
         </p>
         <p>
-        The menu <b>Options &rarr; Log Viewer</b> displays the log file in
a bottom pane on main JMeter window.
+        The menu <menuchoice><guimenuitem>Options</guimenuitem><guimenuitem>Log
Viewer</guimenuitem></menuchoice>
+        displays the log file in a bottom pane on main JMeter window.
         </p>
         <p>
         In the GUI mode, the number of error/fatal messages logged in the log file is displayed
at top-right.



Mime
View raw message