mirror of https://github.com/apache/jmeter.git
Fixing various bugs
updating documentation git-svn-id: https://svn.apache.org/repos/asf/jakarta/jmeter/trunk@322817 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Stover
parent
f9c45a1cef
commit
6734326775
|
|
@ -1,81 +1,112 @@
|
|||
<?xml version="1.0"?>
|
||||
|
||||
<ThreadGroup name="URL Re-writing Example" numThreads="1" rampUp="0">
|
||||
<controllers>
|
||||
<LoopController type="org.apache.jmeter.control.LoopController" name="Loop Controller" iterations="-1">
|
||||
<configElements>
|
||||
</configElements>
|
||||
<controllers>
|
||||
<Controller type="org.apache.jmeter.control.ModifyController" name="Modification Controller">
|
||||
<configElements>
|
||||
<ConfigElement type="org.apache.jmeter.protocol.http.modifier.AnchorModifier">
|
||||
</ConfigElement>
|
||||
</configElements>
|
||||
<controllers>
|
||||
<HttpTestSample type="org.apache.jmeter.protocol.http.control.HttpTestSample" name="Login" getImages="false">
|
||||
<defaultUrl>
|
||||
<ConfigElement type="org.apache.jmeter.protocol.http.config.MultipartUrlConfig">
|
||||
<property name="port">80</property>
|
||||
<property name="PROTOCOL">http</property>
|
||||
<property name="domain">my.server.com</property>
|
||||
<property name="arguments"><Arguments>
|
||||
<argument name="SESSION_ID"> .*</argument>
|
||||
<argument name="username"> user</argument>
|
||||
<argument name="password"> password</argument>
|
||||
</Arguments>
|
||||
</property>
|
||||
<property name="path">/main.jsp</property>
|
||||
<property name="method">POST</property>
|
||||
</ConfigElement></defaultUrl>
|
||||
<configElements>
|
||||
</configElements>
|
||||
<controllers>
|
||||
</controllers>
|
||||
</HttpTestSample>
|
||||
|
||||
<HttpTestSample type="org.apache.jmeter.protocol.http.control.HttpTestSample" name="Do Something interesting" getImages="false">
|
||||
<defaultUrl>
|
||||
<ConfigElement type="org.apache.jmeter.protocol.http.config.MultipartUrlConfig">
|
||||
<property name="PROTOCOL">http</property>
|
||||
<property name="domain">my.server.com</property>
|
||||
<property name="arguments"><Arguments>
|
||||
<argument name="SESSION_ID"> .*</argument>
|
||||
</Arguments>
|
||||
</property>
|
||||
<property name="path">/something_interesting.jsp</property>
|
||||
<property name="method">GET</property>
|
||||
</ConfigElement></defaultUrl>
|
||||
<configElements>
|
||||
</configElements>
|
||||
<controllers>
|
||||
</controllers>
|
||||
</HttpTestSample>
|
||||
|
||||
<HttpTestSample type="org.apache.jmeter.protocol.http.control.HttpTestSample" name="Another Interesting Request" getImages="false">
|
||||
<defaultUrl>
|
||||
<ConfigElement type="org.apache.jmeter.protocol.http.config.MultipartUrlConfig">
|
||||
<property name="PROTOCOL">http</property>
|
||||
<property name="domain">my.server.com</property>
|
||||
<property name="arguments"><Arguments>
|
||||
<argument name="SESSION_ID"> .*</argument>
|
||||
</Arguments>
|
||||
</property>
|
||||
<property name="path">/another.jsp</property>
|
||||
<property name="method">POST</property>
|
||||
</ConfigElement></defaultUrl>
|
||||
<configElements>
|
||||
</configElements>
|
||||
<controllers>
|
||||
</controllers>
|
||||
</HttpTestSample>
|
||||
|
||||
</controllers>
|
||||
</Controller>
|
||||
</controllers>
|
||||
</LoopController>
|
||||
</controllers>
|
||||
<timers>
|
||||
</timers>
|
||||
<listeners>
|
||||
</listeners>
|
||||
</ThreadGroup>
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<node>
|
||||
<testelement class="org.apache.jmeter.threads.ThreadGroup">
|
||||
<property name="TestElement.name">URL Re-writing Example</property>
|
||||
<property name="TestElement.test_class">org.apache.jmeter.threads.ThreadGroup</property>
|
||||
<testelement name="ThreadGroup.main_controller" class="org.apache.jmeter.control.LoopController">
|
||||
<property name="TestElement.test_class">org.apache.jmeter.control.LoopController</property>
|
||||
<property name="TestElement.name">Loop Controller</property>
|
||||
<property name="LoopController.continue_forever">false</property>
|
||||
<property name="LoopController.loops">-1</property>
|
||||
<property name="TestElement.gui_class">org.apache.jmeter.control.gui.LoopControlPanel</property>
|
||||
</testelement>
|
||||
<property name="ThreadGroup.num_threads">1</property>
|
||||
<property name="ThreadGroup.ramp_time">0</property>
|
||||
<property name="TestElement.gui_class">org.apache.jmeter.threads.gui.ThreadGroupGui</property>
|
||||
</testelement>
|
||||
<node>
|
||||
<testelement class="org.apache.jmeter.control.GenericController">
|
||||
<property name="TestElement.test_class">org.apache.jmeter.control.GenericController</property>
|
||||
<property name="TestElement.name">Simple Controller</property>
|
||||
<property name="TestElement.gui_class">org.apache.jmeter.control.gui.LogicControllerGui</property>
|
||||
</testelement>
|
||||
<node>
|
||||
<testelement class="org.apache.jmeter.protocol.http.sampler.HTTPSampler">
|
||||
<property name="TestElement.test_class">org.apache.jmeter.protocol.http.sampler.HTTPSampler</property>
|
||||
<property name="TestElement.name">Login</property>
|
||||
<property name="HTTPSampler.method">POST</property>
|
||||
<property name="HTTPSampler.port">80</property>
|
||||
<property name="HTTPSampler.mimetype"> </property>
|
||||
<collection name="AbstractSampler.assertions" class="java.util.ArrayList"/>
|
||||
<testelement name="HTTPsampler.Arguments" class="org.apache.jmeter.config.Arguments">
|
||||
<property name="TestElement.test_class">org.apache.jmeter.config.Arguments</property>
|
||||
<property name="TestElement.name"> </property>
|
||||
<collection name="Arguments.arguments" class="java.util.ArrayList">
|
||||
<testelement class="org.apache.jmeter.config.Argument">
|
||||
<property name="Argument.name">username</property>
|
||||
<property name="Argument.value">user</property>
|
||||
</testelement>
|
||||
<testelement class="org.apache.jmeter.config.Argument">
|
||||
<property name="Argument.name">password</property>
|
||||
<property name="Argument.value">password</property>
|
||||
</testelement>
|
||||
</collection>
|
||||
<property name="TestElement.gui_class">org.apache.jmeter.config.gui.ArgumentsPanel</property>
|
||||
</testelement>
|
||||
<property name="HTTPSampler.follow_redirects">true</property>
|
||||
<property name="HTTPSampler.protocol">http</property>
|
||||
<property name="HTTPSampler.FILE_FIELD"> </property>
|
||||
<property name="HTTPSampler.path">/main.jsp</property>
|
||||
<property name="HTTPSampler.use_keepalive">true</property>
|
||||
<property name="HTTPSampler.domain">my.server.com</property>
|
||||
<property name="TestElement.gui_class">org.apache.jmeter.protocol.http.control.gui.HttpTestSampleGui</property>
|
||||
<property name="HTTPSampler.FILE_NAME"> </property>
|
||||
</testelement>
|
||||
</node>
|
||||
<node>
|
||||
<testelement class="org.apache.jmeter.protocol.http.sampler.HTTPSampler">
|
||||
<property name="TestElement.test_class">org.apache.jmeter.protocol.http.sampler.HTTPSampler</property>
|
||||
<property name="TestElement.name">Do Something interesting</property>
|
||||
<property name="HTTPSampler.method">GET</property>
|
||||
<property name="HTTPSampler.mimetype"> </property>
|
||||
<collection name="AbstractSampler.assertions" class="java.util.ArrayList"/>
|
||||
<testelement name="HTTPsampler.Arguments" class="org.apache.jmeter.config.Arguments">
|
||||
<property name="TestElement.test_class">org.apache.jmeter.config.Arguments</property>
|
||||
<property name="TestElement.name"> </property>
|
||||
<collection name="Arguments.arguments" class="java.util.ArrayList"/>
|
||||
<property name="TestElement.gui_class">org.apache.jmeter.config.gui.ArgumentsPanel</property>
|
||||
</testelement>
|
||||
<property name="HTTPSampler.follow_redirects">true</property>
|
||||
<property name="HTTPSampler.protocol">http</property>
|
||||
<property name="HTTPSampler.FILE_FIELD"> </property>
|
||||
<property name="HTTPSampler.path">/something_interesting.jsp</property>
|
||||
<property name="HTTPSampler.use_keepalive">true</property>
|
||||
<property name="HTTPSampler.domain">my.server.com</property>
|
||||
<property name="TestElement.gui_class">org.apache.jmeter.protocol.http.control.gui.HttpTestSampleGui</property>
|
||||
<property name="HTTPSampler.FILE_NAME"> </property>
|
||||
</testelement>
|
||||
</node>
|
||||
<node>
|
||||
<testelement class="org.apache.jmeter.protocol.http.sampler.HTTPSampler">
|
||||
<property name="TestElement.test_class">org.apache.jmeter.protocol.http.sampler.HTTPSampler</property>
|
||||
<property name="TestElement.name">Another Interesting Request</property>
|
||||
<property name="HTTPSampler.method">POST</property>
|
||||
<property name="HTTPSampler.mimetype"> </property>
|
||||
<collection name="AbstractSampler.assertions" class="java.util.ArrayList"/>
|
||||
<testelement name="HTTPsampler.Arguments" class="org.apache.jmeter.config.Arguments">
|
||||
<property name="TestElement.test_class">org.apache.jmeter.config.Arguments</property>
|
||||
<property name="TestElement.name"> </property>
|
||||
<collection name="Arguments.arguments" class="java.util.ArrayList"/>
|
||||
<property name="TestElement.gui_class">org.apache.jmeter.config.gui.ArgumentsPanel</property>
|
||||
</testelement>
|
||||
<property name="HTTPSampler.follow_redirects">true</property>
|
||||
<property name="HTTPSampler.protocol">http</property>
|
||||
<property name="HTTPSampler.FILE_FIELD"> </property>
|
||||
<property name="HTTPSampler.path">/another.jsp</property>
|
||||
<property name="HTTPSampler.use_keepalive">true</property>
|
||||
<property name="HTTPSampler.domain">my.server.com</property>
|
||||
<property name="TestElement.gui_class">org.apache.jmeter.protocol.http.control.gui.HttpTestSampleGui</property>
|
||||
<property name="HTTPSampler.FILE_NAME"> </property>
|
||||
</testelement>
|
||||
</node>
|
||||
<node>
|
||||
<testelement class="org.apache.jmeter.protocol.http.modifier.URLRewritingModifier">
|
||||
<property name="TestElement.test_class">org.apache.jmeter.protocol.http.modifier.URLRewritingModifier</property>
|
||||
<property name="TestElement.name">HTTP URL-Rewriting Modifier</property>
|
||||
<property name="argument_name">SESSION_ID</property>
|
||||
<property name="path_extension">false</property>
|
||||
<property name="TestElement.gui_class">org.apache.jmeter.protocol.http.modifier.gui.URLRewritingModifierGui</property>
|
||||
</testelement>
|
||||
</node>
|
||||
</node>
|
||||
</node>
|
||||
|
|
|
|||
|
|
@ -145,12 +145,12 @@ a new instance).</property>
|
|||
|
||||
<component name="Java Request" index="13.1.4" screenshot="../images/screenshots/java_request.gif">
|
||||
|
||||
<description><p>This sampler lets you control a java class that implements the
|
||||
<description><p>This sampler lets you control a java class that implements the
|
||||
JavaSamplerClient interface. By writing your own implementation of this interface,
|
||||
you can use JMeter to harness multiple threads, input parameter control, and
|
||||
data collection.</p>
|
||||
<p>The pull-down menu provides the list of all such implementations found by
|
||||
JMeter in its classpath. The parameters can then be specified in the
|
||||
JMeter in its classpath. The parameters can then be specified in the
|
||||
table below - as defined by your implementation. A simple example (SleepTest) is
|
||||
provided.</p></description>
|
||||
|
||||
|
|
@ -328,7 +328,7 @@ is configured to store the results in a file named "simple-test.dat" in the curr
|
|||
instead of going in order through its sub-controllers and samplers, it picks one
|
||||
at random at each pass.</p>
|
||||
<note>Interactions between multiple controllers can yield complex behavior.
|
||||
This is particularly true of the Random Controller. Experiment before you assume
|
||||
This is particularly true of the Random Controller. Experiment before you assume
|
||||
what results any given interaction will give</note>
|
||||
</description>
|
||||
<properties>
|
||||
|
|
@ -567,57 +567,9 @@ resource requires query string parameters, add them below in the
|
|||
<description></description>
|
||||
</component>
|
||||
|
||||
<component index="13.4.9" name="HTML Link Parser" anchor="html_link_parser">
|
||||
<description>
|
||||
<p>This modifier parses HTML response from the server and extracts
|
||||
links and forms. A URL test sample that passes through this modifier will be examined to
|
||||
see if it "matches" any of the links or forms extracted
|
||||
from the immediately previous response. It would then replace the values in the URL
|
||||
test sample with appropriate values from the matching link or form. Perl-type regular
|
||||
expressions are used to find matches.</p>
|
||||
</description>
|
||||
|
||||
<example title="Spidering Example" anchor="spider_example">
|
||||
<p>Consider a simple example: let's say you wanted JMeter to "spider" through your site,
|
||||
hitting link after link parsed from the HTML returned from your server (this is not
|
||||
actually the most useful thing to do, but it serves as a good example). You would create
|
||||
a <complink anchor="modification_manager" name="Modification Manager"/>, and add the "HTML Link Parser" to it. Then, create a
|
||||
Web Test controller, and set the domain to ".*", and the path likewise. This will
|
||||
cause your test sample to match with any link found on the returned pages. If you wanted to
|
||||
restrict the spidering to a particular domain, then change the domain value
|
||||
to the one you want. Then, only links to that domain will be followed.
|
||||
</p>
|
||||
</example>
|
||||
|
||||
<example title="Poll Example" anchor="poll_example">
|
||||
<p>A more useful example: given a web polling application, you might have a page with
|
||||
several poll options as radio buttons for the user to select. Let's say the values
|
||||
of the poll options are very dynamic - maybe user generated. If you wanted JMeter to
|
||||
test the poll, you could either create test samples with hardcoded values chosen, or you
|
||||
could let the HTML Link Parser parse the form, and insert a random poll option into
|
||||
your URL test sample. To do this, follow the above example, except, when configuring
|
||||
your Web Test controller's URL options, be sure to choose "POST" as the
|
||||
method. Put in hard-coded values for the domain, path, and any additional form parameters.
|
||||
Then, for the actual radio button parameter, put in the name (let's say it's called "poll_choice"),
|
||||
and then ".*" for the value of that parameter. When the modifier examines
|
||||
this URL test sample, it will find that it "matches" the poll form (and
|
||||
it shouldn't match any other form, given that you've specified all the other aspects of
|
||||
the URL test sample), and it will replace your form parameters with the matching
|
||||
parameters from the form. Since the regular expression ".*" will match with
|
||||
anything, the modifier will probably have a list of radio buttons to choose from. It
|
||||
will choose at random, and replace the value in your URL test sample. Each time through
|
||||
the test, a new random value will be chosen.</p>
|
||||
|
||||
<figure image="../images/screenshots/modification.gif">Figure 8 - Online Poll Example</figure>
|
||||
|
||||
<note>One important thing to remember is that you must create a test sample immediately
|
||||
prior that will return an HTML page with the links and forms that are relevant to
|
||||
your dynamic test sample.</note>
|
||||
</example>
|
||||
|
||||
</component>
|
||||
|
||||
<component index="13.4.10" name="HTTP Header Manager" screenshot="../images/screenshots/http-config/http-header-manager.gif">
|
||||
<component index="13.4.9" name="HTTP Header Manager" screenshot="../images/screenshots/http-config/http-header-manager.gif">
|
||||
<description><p>The Header Manager lets you add or override HTTP request headers.</p>
|
||||
</description>
|
||||
|
||||
|
|
@ -729,8 +681,60 @@ to the random delay.</property>
|
|||
</component>
|
||||
</section>
|
||||
|
||||
<section name="13.7 Miscellaneous Features" anchor="Miscellaneous_Features">
|
||||
<component index="13.7.1" name="Data Analyzer" screenshot="../images/screenshots/data_analyzer.gif">
|
||||
<section name="13.7 Modifiers" anchor="Modifiers">
|
||||
<component index="13.7.1" name="HTML Link Parser" anchor="html_link_parser">
|
||||
<description>
|
||||
<p>This modifier parses HTML response from the server and extracts
|
||||
links and forms. A URL test sample that passes through this modifier will be examined to
|
||||
see if it "matches" any of the links or forms extracted
|
||||
from the immediately previous response. It would then replace the values in the URL
|
||||
test sample with appropriate values from the matching link or form. Perl-type regular
|
||||
expressions are used to find matches.</p>
|
||||
</description>
|
||||
|
||||
<example title="Spidering Example" anchor="spider_example">
|
||||
<p>Consider a simple example: let's say you wanted JMeter to "spider" through your site,
|
||||
hitting link after link parsed from the HTML returned from your server (this is not
|
||||
actually the most useful thing to do, but it serves as a good example). You would create
|
||||
a <complink anchor="modification_manager" name="Modification Manager"/>, and add the "HTML Link Parser" to it. Then, create a
|
||||
Web Test controller, and set the domain to ".*", and the path likewise. This will
|
||||
cause your test sample to match with any link found on the returned pages. If you wanted to
|
||||
restrict the spidering to a particular domain, then change the domain value
|
||||
to the one you want. Then, only links to that domain will be followed.
|
||||
</p>
|
||||
</example>
|
||||
|
||||
<example title="Poll Example" anchor="poll_example">
|
||||
<p>A more useful example: given a web polling application, you might have a page with
|
||||
several poll options as radio buttons for the user to select. Let's say the values
|
||||
of the poll options are very dynamic - maybe user generated. If you wanted JMeter to
|
||||
test the poll, you could either create test samples with hardcoded values chosen, or you
|
||||
could let the HTML Link Parser parse the form, and insert a random poll option into
|
||||
your URL test sample. To do this, follow the above example, except, when configuring
|
||||
your Web Test controller's URL options, be sure to choose "POST" as the
|
||||
method. Put in hard-coded values for the domain, path, and any additional form parameters.
|
||||
Then, for the actual radio button parameter, put in the name (let's say it's called "poll_choice"),
|
||||
and then ".*" for the value of that parameter. When the modifier examines
|
||||
this URL test sample, it will find that it "matches" the poll form (and
|
||||
it shouldn't match any other form, given that you've specified all the other aspects of
|
||||
the URL test sample), and it will replace your form parameters with the matching
|
||||
parameters from the form. Since the regular expression ".*" will match with
|
||||
anything, the modifier will probably have a list of radio buttons to choose from. It
|
||||
will choose at random, and replace the value in your URL test sample. Each time through
|
||||
the test, a new random value will be chosen.</p>
|
||||
|
||||
<figure image="../images/screenshots/modification.gif">Figure 8 - Online Poll Example</figure>
|
||||
|
||||
<note>One important thing to remember is that you must create a test sample immediately
|
||||
prior that will return an HTML page with the links and forms that are relevant to
|
||||
your dynamic test sample.</note>
|
||||
</example>
|
||||
|
||||
</component>
|
||||
</section>
|
||||
|
||||
<section name="13.8 Miscellaneous Features" anchor="Miscellaneous_Features">
|
||||
<component index="13.8.1" name="Data Analyzer" screenshot="../images/screenshots/data_analyzer.gif">
|
||||
<description><p>The Data Analyzer presents a graphical view of data stored using the <complink name="File Reporter"/>.</p>
|
||||
<p>To use the Data Analyzer, goto the Report --> Analyze Data File main menu option. Then,
|
||||
when prompted, select the file where the data is stored. JMeter will present the data
|
||||
|
|
@ -738,7 +742,7 @@ as a graph with multiple lines. Each line represents a different HTTP Request f
|
|||
its response times.</p></description>
|
||||
</component>
|
||||
|
||||
<component index="13.7.2" name="SSL Manager" screenshot="">
|
||||
<component index="13.8.2" name="SSL Manager" screenshot="">
|
||||
<p>
|
||||
The SSL Manager is a way to select a client certificate so that you can test
|
||||
applications that use Public Key Infrastructure (PKI). In order to use it,
|
||||
|
|
|
|||
Loading…
Reference in New Issue