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 ms...@apache.org on 2002/03/07 15:19:09 UTC
cvs commit: jakarta-jmeter/xdocs/usermanual best-practices.xml
mstover1 02/03/07 06:19:09
Modified: docs running.html
docs/usermanual best-practices.html
xdocs/usermanual best-practices.xml
Log:
Minor documentation update
Revision Changes Path
1.34 +0 -0 jakarta-jmeter/docs/running.html
Index: running.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/running.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- running.html 6 Mar 2002 12:04:18 -0000 1.33
+++ running.html 7 Mar 2002 14:19:09 -0000 1.34
@@ -243,7 +243,7 @@
<br >
</br>
-$Id: running.html,v 1.33 2002/03/06 12:04:18 mstover1 Exp $
+$Id: running.html,v 1.34 2002/03/07 14:19:09 mstover1 Exp $
</font>
<br >
1.11 +21 -16 jakarta-jmeter/docs/usermanual/best-practices.html
Index: best-practices.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/best-practices.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- best-practices.html 6 Mar 2002 03:52:15 -0000 1.10
+++ best-practices.html 7 Mar 2002 14:19:09 -0000 1.11
@@ -190,24 +190,29 @@
test case "rough drafts".
</p>
<p >
- The test cases will likely need to be further modified. For instance, there may
-have been some dynamic data in one or more of the samples. If so, these samples will
- need to be put under a
- <a href="../usermanual/component_reference.html#Modification_Manager">Modification Manager</a>
- . Currently, there is
- no convenient way to do this other than saving the samples temporarily, deleting them, adding
-the Modification Manager, and then reloading the saved samples into the Modification Manager.
-This will be fixed in 1.8.
+ One of the most useful features of the Proxy Server is that you can abstract out
+certain common elements from the recorded samples. By attaching an
+ <a href="../usermanual/component_reference.html#HTTP_Request_Defaults">HTTP Request Defaults</a>
+ ,
+with the "domain" property specified (eg jakarta.apache.org), to your
+ <a href="../usermanual/component_reference.html#Simple_Controller">Simple Controller</a>
+ ,
+you can direct JMeter to:
</p>
+ <ol >
+ <li >
+ Only record samples with matching "domain" fields under this Controller, and
+ </li>
+
+
+ <li >
+ Remove the "domain" field from the recorded sample.
+ </li>
+
+
+ </ol>
<p >
- You may also want to put any login pages within a
- <a href="../usermanual/component_reference.html#Once_Only_Controller">Once Only Controller</a>
- ,
-so that the login action is done only once per test. Alternatively, you might put all
-the samples but the login page within a
- <a href="../usermanual/component_reference.html#Loop_Controller">Loop Controller</a>
- , to execute
-X number of times before repeating the login request.
+ You can do the same with the "Path" field.
</p>
</blockquote>
</p>
1.4 +8 -10 jakarta-jmeter/xdocs/usermanual/best-practices.xml
Index: best-practices.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/best-practices.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- best-practices.xml 6 Mar 2002 03:52:03 -0000 1.3
+++ best-practices.xml 7 Mar 2002 14:19:09 -0000 1.4
@@ -52,16 +52,14 @@
definite series of steps, save the entire test case in an appropriately named file. Then, wipe
clean and start a new test case. By doing this, you can quickly record a large number of
test case "rough drafts".</p>
-<p>The test cases will likely need to be further modified. For instance, there may
-have been some dynamic data in one or more of the samples. If so, these samples will
- need to be put under a <complink name="Modification Manager"/>. Currently, there is
- no convenient way to do this other than saving the samples temporarily, deleting them, adding
-the Modification Manager, and then reloading the saved samples into the Modification Manager.
-This will be fixed in 1.8.</p>
-<p>You may also want to put any login pages within a <complink name="Once Only Controller"/>,
-so that the login action is done only once per test. Alternatively, you might put all
-the samples but the login page within a <complink name="Loop Controller"/>, to execute
-X number of times before repeating the login request.</p>
+<p>One of the most useful features of the Proxy Server is that you can abstract out
+certain common elements from the recorded samples. By attaching an <complink name="HTTP Request Defaults"/>,
+with the "domain" property specified (eg jakarta.apache.org), to your <complink name="Simple Controller"/>,
+you can direct JMeter to:</p>
+<ol><li>Only record samples with matching "domain" fields under this Controller, and</li>
+<li>Remove the "domain" field from the recorded sample.</li>
+</ol>
+<p>You can do the same with the "Path" field.</p>
</section>
</body>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>