mirror of https://github.com/apache/jmeter.git
189 lines
16 KiB
HTML
189 lines
16 KiB
HTML
<!DOCTYPE html SYSTEM "about:legacy-compat">
|
|
<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-15"><title>Apache JMeter
|
|
-
|
|
User's Manual: Building a Simple Database Test Plan</title><meta name="viewport" content="width=device-width, initial-scale=1"><link href="http://fonts.googleapis.com/css?family=Merriweather:400normal" rel="stylesheet" type="text/css"><link rel="stylesheet" type="text/css" href="../css/new-style.css"><link rel="apple-touch-icon-precomposed" href="../images/apple-touch-icon.png"><link rel="icon" href="../images/favicon.png"><meta name="msapplication-TileColor" content="#ffffff"><meta name="msapplication-TileImage" content="../images/mstile-144x144.png"><meta name="theme-color" content="#ffffff"></head><body role="document"><a href="#content" class="hidden">Main content</a><div class="header"><!--
|
|
APACHE LOGO
|
|
--><div><a href="http://www.apache.org"><img title="Apache Software Foundation" class="logo" src="../images/asf-logo.svg" alt="Logo ASF"></a></div><!--
|
|
PROJECT LOGO
|
|
--><div><a href="http://jmeter.apache.org/"><img class="logo" src="../images/logo.svg" alt="Apache JMeter"></a></div><div class="banner"><iframe src="http://www.apache.org/ads/bannerbar.html" style="border-width:0;" frameborder="0" scrolling="no"></iframe><div class="clear"></div></div></div><div class="nav"><div class="social menu"><div align="center"><a href="https://twitter.com/ApacheJMeter" class="twitter-follow-button" data-show-count="false" data-lang="en-gb">Follow</a><script>(function(d,s,id){
|
|
var js,
|
|
fjs=d.getElementsByTagName(s)[0],
|
|
p=/^http:/.test(d.location)?'http':'https';
|
|
if (!d.getElementById(id)) {
|
|
js=d.createElement(s);
|
|
js.id=id;
|
|
js.src=p+'://platform.twitter.com/widgets.js';
|
|
fjs.parentNode.insertBefore(js,fjs);
|
|
}
|
|
})(document, 'script', 'twitter-wjs');
|
|
</script></div><div align="center"><a href="https://github.com/apache/jmeter"><img alt="star this repo" src="http://githubbadges.com/star.svg?user=apache&repo=jmeter&style=flat"></a><a href="https://github.com/apache/jmeter/fork"><img alt="fork this repo" src="http://githubbadges.com/fork.svg?user=apache&repo=jmeter&style=flat"></a></div><div align="center"><a href="https://maven-badges.herokuapp.com/maven-central/org.apache.jmeter/ApacheJMeter"><img alt="Maven Central" src="https://maven-badges.herokuapp.com/maven-central/org.apache.jmeter/ApacheJMeter/badge.svg"></a></div></div><ul class="menu"><li onClick="return true"><div class="menu-title">About</div><ul><li><a href="../index.html">Overview</a></li><li><a href="http://www.apache.org/licenses/">License</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Download</div><ul><li><a href="../download_jmeter.cgi">Download Releases</a></li><li><a href="../nightly.html">Developer (Nightly) Builds</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Documentation</div><ul><li><a href="../changes.html">Changes per version</a></li><li><a href="../usermanual/get-started.html">Get Started</a></li><li><a href="../usermanual/index.html">User Manual</a></li><li><a href="../usermanual/best-practices.html">Best Practices</a></li><li><a href="../usermanual/component_reference.html">Component Reference</a></li><li><a href="../usermanual/functions.html">Functions Reference</a></li><li><a href="../api/index.html">Javadocs</a></li><li><a href="../building.html">Building JMeter and Add-Ons</a></li><li><a href="http://wiki.apache.org/jmeter">JMeter Wiki</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterFAQ">FAQ (Wiki)</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Tutorials (PDF format)</div><ul><li><a href="../usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed Testing</a></li><li><a href="../usermanual/jmeter_proxy_step_by_step.pdf">Recording Tests</a></li><li><a href="../usermanual/junitsampler_tutorial.pdf">JUnit Sampler</a></li><li><a href="../usermanual/jmeter_accesslog_sampler_step_by_step.pdf">Access Log Sampler</a></li><li><a href="../extending/jmeter_tutorial.pdf">Extending JMeter</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Community</div><ul><li><a href="../issues.html">Issue Tracking</a></li><li><a href="../mail.html">Mailing Lists</a></li><li><a href="../svnindex.html">Source Repositories</a></li><li><a href="../building.html">Building and Contributing</a></li><li><a href="https://projects.apache.org/project.html?jmeter">Project info at Apache</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterCommitters">Contributors</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Foundation</div><ul><li><a href="http://www.apache.org/">ASF</a></li><li><a href="http://www.apache.org/foundation/getinvolved.html">Get Involved in the ASF</a></li><li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li><li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></li></ul></div><div class="main" id="content"><ul class="pagelinks"><li><a href="build-adv-web-test-plan.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="build-ftp-test-plan.html">Next ></a></li></ul><div class="section"><h1 id="building">7. Building a Database Test Plan<a class="sectionlink" href="#building" title="Link to here">¶</a></h1>
|
|
<p>In this section, you will learn how to create a basic
|
|
<a href="build-test-plan.html">Test Plan</a> to test a database server.
|
|
You will create fifty users that send 2 SQL requests to the database server.
|
|
Also, you will tell the users to run their tests 100 times. So, the total number
|
|
of requests is (50 users) x (2 requests) x (repeat 100 times) = 10'000 JDBC requests.
|
|
To construct the Test Plan, you will use the following elements:
|
|
<a href="test_plan.html#thread_group">Thread Group</a>,
|
|
<a href="../usermanual/component_reference.html#JDBC_Request">JDBC Request</a>, <a href="../usermanual/component_reference.html#Summary_Report">Summary Report</a>.</p>
|
|
|
|
<div class="clear"></div><div class="note">This example uses the MySQL database driver.
|
|
To use this driver, its containing .jar file (ex. mysql-connector-java-X.X.X-bin.jar) must be copied to the JMeter
|
|
<b>./lib</b> directory (see <a href="get-started.html#classpath">JMeter's Classpath</a>
|
|
for more details).</div><div class="clear"></div>
|
|
|
|
</div><div class="section"><h1 id="adding_users">7.1 Adding Users<a class="sectionlink" href="#adding_users" title="Link to here">¶</a></h1>
|
|
<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 <span class="code">Add</span> menu, and then select
|
|
<span class="menuchoice"><span class="guimenuitem">Add</span> → <span class="guimenuitem">ThreadGroup</span></span>.</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 7.1
|
|
below)</p>
|
|
|
|
<figure><a href="../images/screenshots/jdbctest/threadgroup1.png"><img src="../images/screenshots/jdbctest/threadgroup1.png" width="" height="" alt="
|
|
Figure 7.1. Thread Group with Default Values"></a><figcaption>
|
|
Figure 7.1. Thread Group with Default Values</figcaption></figure>
|
|
|
|
<p>Start by providing a more descriptive name for our Thread Group. In the name
|
|
field, enter JDBC Users.</p>
|
|
|
|
<div class="clear"></div><div class="note">You will need a valid database, database table, and user-level access to that
|
|
table. In the example shown here, the database is 'cloud' and the table name is
|
|
'vm_instance'.</div><div class="clear"></div>
|
|
|
|
<p>Next, increase the number of users to 50.</p>
|
|
|
|
<p>In the next field, the Ramp-Up Period, leave the value of 10
|
|
seconds. This property tells JMeter how long to delay between starting each
|
|
user. For example, if you enter a Ramp-Up Period of 10 seconds, JMeter will
|
|
finish starting all of your users by the end of the 10 seconds. So, if we have
|
|
50 users and a 10 second Ramp-Up Period, then the delay between starting users
|
|
would be 200 milliseconds (10 seconds / 50 users = 0.2 user per second). If you set the
|
|
value to 0, then JMeter will immediately start all of your users.</p>
|
|
|
|
<p>Finally, enter a value of 100 in
|
|
the Loop Count field. This property tells JMeter how many times to repeat your
|
|
test. To have JMeter repeatedly run your Test Plan, select the Forever
|
|
checkbox.</p>
|
|
|
|
<div class="clear"></div><div class="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).</div><div class="clear"></div>
|
|
|
|
<p>See Figure 7.2 for the completed JDBC Users Thread Group.</p>
|
|
|
|
<figure><a href="../images/screenshots/jdbctest/threadgroup2.png"><img src="../images/screenshots/jdbctest/threadgroup2.png" width="" height="" alt="
|
|
Figure 7.2. JDBC Users Thread Group"></a><figcaption>
|
|
Figure 7.2. JDBC Users Thread Group</figcaption></figure>
|
|
|
|
</div><div class="section"><h1 id="adding_requests">7.2 Adding JDBC Requests<a class="sectionlink" href="#adding_requests" title="Link to here">¶</a></h1>
|
|
<p>Now that we have defined our users, it is time to define the tasks that they
|
|
will be performing. In this section, you will specify the JDBC requests to
|
|
perform.</p>
|
|
|
|
<p>Begin by selecting the JDBC Users element. Click your right mouse button
|
|
to get the <b>Add</b> menu, and then select <span class="menuchoice"><span class="guimenuitem">Add</span> → <span class="guimenuitem">Config Element</span> → <span class="guimenuitem">JDBC Connection Configuration</span></span>.
|
|
Then, select this new element to view its Control Panel (see Figure 7.3).</p>
|
|
|
|
<p>Set up the following fields (these assume we will be using a MySQL database called 'cloud'):</p>
|
|
<ul>
|
|
<li>Variable name (here: myDatabase) bound to pool. This needs to uniquely identify the configuration. It is used by the JDBC Sampler to identify the configuration to be used.</li>
|
|
<li>Database URL: jdbc:mysql://ipOfTheServer:3306/cloud</li>
|
|
<li>JDBC Driver class: com.mysql.jdbc.Driver</li>
|
|
<li>Username: the username of database</li>
|
|
<li>Password: password for the username</li>
|
|
</ul>
|
|
<p>The other fields on the screen can be left as the defaults.</p>
|
|
<p>JMeter creates a database connection pool with the configuration settings as specified in the Control Panel.
|
|
The pool is referred to in JDBC Requests in the 'Variable Name' field.
|
|
Several different JDBC Configuration elements can be used, but they must have unique names.
|
|
Every JDBC Request must refer to a JDBC Configuration pool.
|
|
More than one JDBC Request can refer to the same pool.
|
|
</p>
|
|
<figure><a href="../images/screenshots/jdbctest/jdbc-config.png"><img src="../images/screenshots/jdbctest/jdbc-config.png" width="" height="" alt="
|
|
Figure 7.3. JDBC Configuration"></a><figcaption>
|
|
Figure 7.3. JDBC Configuration</figcaption></figure>
|
|
|
|
<p>Selecting the JDBC Users element again. Click your right mouse button
|
|
to get the <b>Add</b> menu, and then select <span class="menuchoice"><span class="guimenuitem">Add</span> → <span class="guimenuitem">Sampler</span> → <span class="guimenuitem">JDBC Request</span></span>.
|
|
Then, select this new element to view its Control Panel (see Figure 7.4).</p>
|
|
|
|
<figure><a href="../images/screenshots/jdbctest/JDBCRequest.png"><img src="../images/screenshots/jdbctest/JDBCRequest.png" width="" height="" alt="
|
|
Figure 7.4. JDBC Request"></a><figcaption>
|
|
Figure 7.4. JDBC Request</figcaption></figure>
|
|
|
|
<p>In our Test Plan, we will make two JDBC requests. The first one is for
|
|
select all 'Running' VM instances, and the second is to select 'Expunging' VM instance (obviously you should
|
|
change these to examples appropriate for your particular database). These
|
|
are illustrated below.</p>
|
|
|
|
<div class="clear"></div><div class="note">JMeter sends requests in the order that you add them to the tree.</div><div class="clear"></div>
|
|
|
|
<p>Start by editing the following properties (see Figure 7.5):
|
|
<ul>
|
|
<li>Change the Name to 'VM Running'.</li>
|
|
<li>Enter the Pool Name: 'myDatabase' (same as in the configuration element)</li>
|
|
<li>Enter the SQL Query String field.</li>
|
|
<li>Enter the Parameter values field with 'Running' value.</li>
|
|
<li>Enter the Parameter types with 'VARCHAR'.</li>
|
|
</ul>
|
|
</p>
|
|
|
|
<figure><a href="../images/screenshots/jdbctest/JDBCRequest2.png"><img src="../images/screenshots/jdbctest/JDBCRequest2.png" width="" height="" alt="
|
|
Figure 7.5. JDBC Request for the first SQL request"></a><figcaption>
|
|
Figure 7.5. JDBC Request for the first SQL request</figcaption></figure>
|
|
|
|
<p>Next, add the second JDBC Request and edit the following properties (see
|
|
Figure 7.6):
|
|
<ul>
|
|
<li>Change the Name to 'VM Expunging'.</li>
|
|
<li>Change the value of Parameter values to 'Expunging'.</li>
|
|
</ul>
|
|
</p>
|
|
|
|
<figure><a href="../images/screenshots/jdbctest/JDBCRequest3.png"><img src="../images/screenshots/jdbctest/JDBCRequest3.png" width="" height="" alt="
|
|
Figure 7.6. JDBC Request for the second request"></a><figcaption>
|
|
Figure 7.6. JDBC Request for the second request</figcaption></figure>
|
|
|
|
</div><div class="section"><h1 id="adding_listener">7.3 Adding a Listener to View/Store the Test Results<a class="sectionlink" href="#adding_listener" title="Link to here">¶</a></h1>
|
|
<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 JDBC requests in a file
|
|
and presenting the results.</p>
|
|
|
|
<p>Select the <i>JDBC Users</i> element and add a <a href="../usermanual/component_reference.html#Summary_Report">Summary Report</a>
|
|
listener (<span class="menuchoice"><span class="guimenuitem">Add</span> → <span class="guimenuitem">Listener</span> → <span class="guimenuitem">Summary Report</span></span>).</p>
|
|
|
|
<p>Save the test plan, and run the test with the menu
|
|
<span class="menuchoice"><span class="guimenuitem">Run</span> → <span class="guimenuitem">Start</span></span> or
|
|
<span class="keycombo"><span class="keysym">Ctrl</span> + <span class="keysym">R</span></span>
|
|
</p>
|
|
|
|
<p>The listener shows the results.</p>
|
|
|
|
<figure><a href="../images/screenshots/jdbctest/jdbc-results.png"><img src="../images/screenshots/jdbctest/jdbc-results.png" width="" height="" alt="
|
|
Figure 7.7. Graph results Listener"></a><figcaption>
|
|
Figure 7.7. Graph results Listener</figcaption></figure>
|
|
|
|
</div><ul class="pagelinks"><li><a href="build-adv-web-test-plan.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="build-ftp-test-plan.html">Next ></a></li></ul></div><div class="footer"><div class="copyright">
|
|
Copyright ©
|
|
1999 –
|
|
2016
|
|
, Apache Software Foundation
|
|
</div><div class="trademarks">Apache, Apache JMeter, JMeter, the Apache
|
|
feather, and the Apache JMeter logo are
|
|
trademarks of the
|
|
Apache Software Foundation.
|
|
</div></div></body></html> |