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 wo...@apache.org on 2004/01/07 14:36:01 UTC
cvs commit: jakarta-jmeter/xdocs/usermanual build-ws-test-plan.xml
woolfel 2004/01/07 05:36:01
Added: xdocs/usermanual build-ws-test-plan.xml
Log:
added rough draft of build-ws-test-plan
still need to update the other docs and add it to index.xml
PR:
Obtained from:
Submitted by:
Reviewed by:
CVS: ----------------------------------------------------------------------
CVS: PR:
CVS: If this change addresses a PR in the problem report tracking
CVS: database, then enter the PR number(s) here.
CVS: Obtained from:
CVS: If this change has been taken from another system, such as NCSA,
CVS: then name the system in this line, otherwise delete it.
CVS: Submitted by:
CVS: If this code has been contributed to Apache by someone else; i.e.,
CVS: they sent us a patch or a new module, then include their name/email
CVS: address here. If this is your work then delete this line.
CVS: Reviewed by:
CVS: If we are doing pre-commit code reviews and someone else has
CVS: reviewed your changes, include their name(s) here.
CVS: If you have not had it reviewed then delete this line.
Revision Changes Path
1.1 jakarta-jmeter/xdocs/usermanual/build-ws-test-plan.xml
Index: build-ws-test-plan.xml
===================================================================
<?xml version="1.0"?>
<document prev="get-started.html" next="build_ws_test_plan.html" date="$Date: 2004/01/07 13:36:01 $">
<properties>
<title>User's Manual: Building a WebService Test Plan</title>
</properties>
<body>
<section name="10. Building a WebService Test Plan" anchor="building">
<p>In this section, you will learn how to create a
<a href="build-test-plan.html">Test Plan</a> to test a WebService. You will
create five users that send requests to One page.
Also, you will tell the users to run their tests twice. So, the total number of
requests is (5 users) x (1 requests) x (repeat 2 times) = 10 HTTP requests. To
construct the Test Plan, you will use the following elements:
<a href="test_plan.html#thread_group">Thread Group</a>,
<complink name="WebService(SOAP) Request (Alpha Code)"/>, and
<complink name="Graph Results"/>.</p>
</section>
<!--
<p>After starting JMeter, you see three items in the tree: Root (the parent of
all tree elements), Test Plan (you place all of your elements here), and
WorkBench (a temporary place to store your elements while constructing a Test
Plan).</p>-->
<section name="10.1 Adding Users" anchor="adding_users">
<p>The first step you want to do with every JMeter Test Plan is to add a
<a href="test_plan.html#thread_group">Thread Group</a> element. 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 Add menu, and then select
Add --> ThreadGroup.</p>
<p>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.</p>
<p>Next, you need to modify the default properties. Select the Thread Group element
in the tree, if you have not already selected it. You should now see the Thread
Group Control Panel in the right section of the JMeter window (see Figure 10.1
below)</p>
<figure image="webtest/threadgroup.png">
Figure 10.1. Thread Group with Default Values</figure>
<p>Start by providing a more descriptive name for our Thread Group. In the name
field, enter Jakarta Users.</p>
<p>Next, increase the number of users (called threads) 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
user. For example, if you enter a Ramp-Up Period of 5 seconds, JMeter will
finish starting all of your users by the end of the 5 seconds. So, if we have
5 users and a 5 second Ramp-Up Period, then the delay between starting users
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
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
checkbox.</p>
<note>In most applications, you have to manually accept
changes you make in a Control Panel. However, in JMeter, the Control Panel
automatically accepts your changes as you make them. If you change the
name of an element, the tree will be updated with the new text after you
leave the Control Panel (for example, when selecting another tree element).</note>
<p>See Figure 10.2 for the completed Jakarta Users Thread Group.</p>
<figure image="webtest/threadgroup2.png">
Figure 10.2. Jakarta Users Thread Group</figure>
</section>
<section name="10.2 Adding WebService Requests" anchor="adding_requests">
<p>In our Test Plan, we will use a .NET webservice. Since you're using
the webservice sampler, we won't go into the details of writing a
webservice. If you don't know how to write a webservice, google for
webservice and familiarize yourself with writing webservices for
Java and .NET. It should be noted there is a significant difference
between how .NET and Java implement webservices. .NET webservices are
document centric, whereas Java webservices tend to be RPC centric.
Neither approach is perfect and each has limitations.</p>
<note>JMeter sends requests in the order that they appear in the tree.</note>
<p>Start by adding the sampler <complink name="WebService(SOAP) Request (Alpha Code)"/>
to the Jakarta Users element (Add --> Sampler --> WebService(SOAP) Request
(Alpha Code) ).
Then, select the webservice Request element in the tree and edit the following properties
(see Figure 10.5):
<ol>
<li>Change the Name field to "WebService(SOAP) Request (Alpha Code)".</li>
<li>Enter the WSDL URL and click "Load WSDL".</li>
</ol>
</p>
<figure image="webservice_sampler.png">
Figure 10.3. Webservice Request</figure>
<p>If the WSDL file was loaded correctly, the "Web Methods" drop down should now
be populated. If the drop down remains blank, it means there was a problem
getting the WSDL. You can test the WSDL file using a browser that reads XML.
For example, if you're testing an IIS webservice it will look like this:
http://localhost/myWebService/Service.asmx?WSDL.</p>
<p>Next, select the web method and click "Configure". The sampler should
populate the "URL" and "SOAPAction" text fields. Assuming the WSDL is valid,
the correct soap action should be entered.
</p>
<p>The last step is to paste the SOAP message in the "SOAP/XML-RPC Data"
text area. You can optionally save the soap message to a file and browse
to the location. For convienance, there is a third option of using a
message folder. The sampler will randomly select files from a given
folder and use the text for the soap message.</p>
</section>
<section name="10.3 Adding a Listener to View Store the Test Results" anchor="adding_listener">
<p>The final element you need to add to your Test Plan is a
<a href="component_reference.html#listeners">Listener</a>. This element is
responsible for storing all of the results of your HTTP requests in a file and presenting
a visual model of the data.</p>
<p>Select the Jakarta Users element and add a <complink name="Graph Results"/> listener (Add --> Listener
--> Graph Results). Next, you need to specify a directory and filename of the
output file. You can either type it into the filename field, or select the
Browse button and browse to a directory and then enter a filename.</p>
<figure image="graph_results.png">
Figure 10.7. Graph Results Listener</figure>
</section>
<section name="10.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>
</section>
<section name="10.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>
<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>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org