Modified: jmeter/trunk/docs/usermanual/best-practices.html URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/best-practices.html?rev=1808646&r1=1808645&r2=1808646&view=diff ============================================================================== --- jmeter/trunk/docs/usermanual/best-practices.html (original) +++ jmeter/trunk/docs/usermanual/best-practices.html Sun Sep 17 18:22:16 2017 @@ -1,17 +1,215 @@ <!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 +<html lang="en"> +<head> +<META http-equiv="Content-Type" content="text/html; charset=iso-8859-15"> +<title>Apache JMeter - - User's Manual: Best Practices</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 href="https://maxcdn.bootstrapcdn.com/font-awesome/4.6.1/css/font-awesome.min.css"; 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"><!-- + User's Manual: Best Practices</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 href="https://maxcdn.bootstrapcdn.com/font-awesome/4.6.1/css/font-awesome.min.css"; 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="asf-logo logo" src="../images/asf-logo.svg" alt="Logo ASF"></a></div><!-- + --> +<div> +<a href="http://www.apache.org";><img title="Apache Software Foundation" class="asf-logo 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"><a href="http://www.apache.org/events/current-event.html";><img src="http://www.apache.org/events/current-event-234x60.png"; alt="Current Apache event teaser"></a><div class="clear"></div></div></div><div class="nav"><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="../changes.html">Release Notes</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Documentation</div><ul><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="../usermanual/properties_reference.html">Properties Reference</a></li><li><a href="../changes_history.html">Change History</a></li><li><a href="../api/index.html">Javadocs</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</div><ul><li><a href="../usermanual/jmeter_distributed_testing_step_by_step.html">Distributed Testing</a></li><li><a href="../usermanual/jmeter_proxy_step_by_step.html">Recording Tests</a></li><li><a href="../usermanual/junitsampler_tutorial.html">JUnit Sampler</a></li><li><a href="../usermanual/jmeter_accesslog_sampler_step_by_step.html">Access Log Sampler</a></li><li><a href="../usermanual/jmeter_tutorial.html">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"><div class="social-media"><ul class="social-media-links"><li class="twitter"><a href="https://twitter.com/ApacheJMeter"; title="Follow us on Twitter"><i class="fa fa-twitter" aria-hidden="true"></i>Twitter</a></li><li class="github"><a href="https://github.com/apache/jmeter"; title="Fork us on github"><i class="fa fa-github" aria-hidden="true"></i>github</a></li></ul></div><ul class="pagelinks"><li><a href="realtime-results.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="boss.html">Next ></a></li></ul><div class="section"><h1 id="best_practices">17. Best Practices<a class="sectionlink" href="#best_practices" title="Link to here">¶</a></h1> -</div><div class="section"><h1 id="use_latest_version">17.1 Always use latest version of JMeter<a class="sectionlink" href="#use_latest_version" title="Link to here">¶</a></h1> + --> +<div> +<a href="http://jmeter.apache.org/";><img class="logo" src="../images/logo.svg" alt="Apache JMeter"></a> +</div> +<div class="banner"> +<a href="http://www.apache.org/events/current-event.html";><img src="http://www.apache.org/events/current-event-234x60.png"; alt="Current Apache event teaser"></a> +<div class="clear"></div> +</div> +</div> +<div class="nav"> +<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="../changes.html">Release Notes</a> +</li> +</ul> +</li> +</ul> +<ul class="menu"> +<li onClick="return true"> +<div class="menu-title">Documentation</div> +<ul> +<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="../usermanual/properties_reference.html">Properties Reference</a> +</li> +<li> +<a href="../changes_history.html">Change History</a> +</li> +<li> +<a href="../api/index.html">Javadocs</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</div> +<ul> +<li> +<a href="../usermanual/jmeter_distributed_testing_step_by_step.html">Distributed Testing</a> +</li> +<li> +<a href="../usermanual/jmeter_proxy_step_by_step.html">Recording Tests</a> +</li> +<li> +<a href="../usermanual/junitsampler_tutorial.html">JUnit Sampler</a> +</li> +<li> +<a href="../usermanual/jmeter_accesslog_sampler_step_by_step.html">Access Log Sampler</a> +</li> +<li> +<a href="../usermanual/jmeter_tutorial.html">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="http://www.apache.org/security/";>Security</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/";>The Apache Software Foundation (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"> +<div class="social-media"> +<ul class="social-media-links"> +<li class="twitter"> +<a href="https://twitter.com/ApacheJMeter"; title="Follow us on Twitter"><i class="fa fa-twitter" aria-hidden="true"></i>Twitter</a> +</li> +<li class="github"> +<a href="https://github.com/apache/jmeter"; title="Fork us on github"><i class="fa fa-github" aria-hidden="true"></i>github</a> +</li> +</ul> +</div> +<ul class="pagelinks"> +<li> +<a href="realtime-results.html">< Prev</a> +</li> +<li> +<a href="../index.html">Index</a> +</li> +<li> +<a href="boss.html">Next ></a> +</li> +</ul> +<div class="section"> +<h1 id="best_practices">16. Best Practices<a class="sectionlink" href="#best_practices" title="Link to here">¶</a> +</h1> + +</div> +<div class="section"> +<h1 id="use_latest_version">16.1 Always use latest version of JMeter<a class="sectionlink" href="#use_latest_version" title="Link to here">¶</a> +</h1> + <p>The performance of JMeter is being constantly improved, so users are highly encouraged to use the most up to date version. <br> Ensure you always read <a href="../changes.html">changes list</a> to be aware of new improvements and components. You should absolutely avoid using versions that are older than 3 versions before the last one. </p> -</div><div class="section"><h1 id="sizing_threads">17.2 Use the correct Number of Threads<a class="sectionlink" href="#sizing_threads" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="sizing_threads">16.2 Use the correct Number of Threads<a class="sectionlink" href="#sizing_threads" title="Link to here">¶</a> +</h1> + <p>Your hardware capabilities as well as the Test Plan design will both impact the number of threads you can effectively run with JMeter. The number will also depend on how fast your server is (a faster server makes JMeter work harder since it returns a response quicker). As with any Load Testing tool, if you don't correctly size @@ -22,17 +220,33 @@ run with JMeter. The number will also d For testing how JMeter performs on a given platform, the JavaTest sampler can be used. It does not require any network access so can give some idea as to the maximum throughput achievable. </p> + <p> JMeter has an option to delay thread creation until the thread starts sampling, i.e. after any thread group delay and the ramp-up time for the thread itself. This allows for a very large total number of threads, provided that not too many are active concurrently. </p> -</div><div class="section"><h1 id="put_cookie_manager">17.3 Where to Put the Cookie Manager<a class="sectionlink" href="#put_cookie_manager" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="put_cookie_manager">16.3 Where to Put the Cookie Manager<a class="sectionlink" href="#put_cookie_manager" title="Link to here">¶</a> +</h1> + <p>See <a href="build-web-test-plan.html#adding_cookie_support">Building a Web Test</a> for information.</p> -</div><div class="section"><h1 id="put_auth_manager">17.4 Where to Put the Authorization Manager<a class="sectionlink" href="#put_auth_manager" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="put_auth_manager">16.4 Where to Put the Authorization Manager<a class="sectionlink" href="#put_auth_manager" title="Link to here">¶</a> +</h1> + <p>See <a href="build-adv-web-test-plan.html#header_manager">Building an Advanced Web Test</a> for information.</p> -</div><div class="section"><h1 id="proxy_server">17.5 Using the HTTP(S) Test Script Recorder<a class="sectionlink" href="#proxy_server" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="proxy_server">16.5 Using the HTTP(S) Test Script Recorder<a class="sectionlink" href="#proxy_server" title="Link to here">¶</a> +</h1> + <p>Refer to <a href="../usermanual/component_reference.html#HTTP(S)_Test_Script_Recorder">HTTP(S) Test Script Recorder</a> for details on setting up the recorder. The most important thing to do is filter out all requests you aren't interested in. For instance, there's no point in recording image requests (JMeter can @@ -40,20 +254,24 @@ be instructed to download all images on These will just clutter your test plan. Most likely, there is an extension all your files share, such as <span class="code">.jsp</span>, <span class="code">.asp</span>, <span class="code">.php</span>, <span class="code">.html</span> or the like. These you should "<span class="code">include</span>" by entering "<span class="code">.*\.jsp</span>" as an "Include Pattern". </p> + <p>Alternatively, you can exclude images by entering "<span class="code">.*\.gif</span>" as an "Exclude Pattern". Depending on your application, this may or may not be a better way to go. You may also have to exclude stylesheets, javascript files, and other included files. Test out your settings to verify you are recording what you want, and then erase and start fresh.</p> + <p>The HTTP(S) Test Script Recorder expects to find a ThreadGroup element with a Recording Controller under it where it will record HTTP Requests to. This conveniently packages all your samples under one controller, which can be given a name that describes the test case.</p> + <p>Now, go through the steps of a Test Case. If you have no pre-defined test cases, use JMeter to record your actions to define your test cases. Once you have finished a 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>One of the most useful features of the HTTP(S) Test Script Recorder is that you can abstract out certain common elements from the recorded samples. By defining some <a href="functions.html">user-defined variables</a> at the Test Plan level or in @@ -63,81 +281,128 @@ server "<span class="code">xxx.example.c "<span class="code">xxx.example.com</span>", and anyplace that value is found in your recorded samples will be replaced with "<span class="code">${server}</span>". -<div class="clear"></div><div class="note">Please note that matching is case-sensitive.</div><div class="clear"></div> +<div class="clear"></div> +<div class="note">Please note that matching is case-sensitive.</div> +<div class="clear"></div> + </p> + <p> If JMeter does not record any samples, check that the browser really is using the proxy. If the browser works OK even if JMeter is not running, then the browser cannot be using the proxy. Some browsers ignore proxy settings for <span class="code">localhost</span> or <span class="code">127.0.0.1</span>; try using the local hostname or IP instead. </p> + <p> The error "<span class="code">unknown_ca</span>" probably means that you are trying to record HTTPS, and the browser has not accepted the JMeter Proxy server certificate. </p> -</div><div class="section"><h1 id="user_variables">17.6 User variables<a class="sectionlink" href="#user_variables" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="user_variables">16.6 User variables<a class="sectionlink" href="#user_variables" title="Link to here">¶</a> +</h1> + <p> Some test plans need to use different values for different users/threads. For example, you might want to test a sequence that requires a unique login for each user. This is easy to achieve with the facilities provided by JMeter. </p> + <p>For example:</p> + <ul> + <li>Create a text file containing the user names and passwords, separated by commas. Put this in the same directory as your test plan. </li> + <li> Add a CSV DataSet configuration element to the test plan. Name the variables <span class="code">USER</span> and <span class="code">PASS</span>. </li> + <li> Replace the login name with <span class="code">${USER}</span> and the password with <span class="code">${PASS}</span> on the appropriate samplers </li> + </ul> + <p>The CSV Data Set element will read a new line for each thread. </p> -</div><div class="section"><h1 id="lean_mean">17.7 Reducing resource requirements<a class="sectionlink" href="#lean_mean" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="lean_mean">16.7 Reducing resource requirements<a class="sectionlink" href="#lean_mean" title="Link to here">¶</a> +</h1> + <p> Some suggestions on reducing resource usage. </p> + <ul> -<li>Use non-GUI mode: <span class="code">jmeter -n -t test.jmx -l test.jtl</span></li> + +<li>Use non-GUI mode: <span class="code">jmeter -n -t test.jmx -l test.jtl</span> +</li> + <li>Use as few Listeners as possible; if using the <span class="code">-l</span> flag as above they can all be deleted or disabled.</li> + <li>Don't use "View Results Tree" or "View Results in Table" listeners during the load test, use them only during scripting phase to debug your scripts.</li> + <li>Rather than using lots of similar samplers, use the same sampler in a loop, and use variables (CSV Data Set) to vary the sample. [The Include Controller does not help here, as it adds all the test elements in the file to the test plan.] </li> + <li>Don't use functional mode</li> + <li>Use CSV output rather than XML</li> + <li>Only save the data that you need</li> + <li>Use as few Assertions as possible</li> + <li>Use the most performing scripting language (see JSR223 section)</li> + </ul> + <p> If your test needs large amounts of data - particularly if it needs to be randomised - create the test data in a file that can be read with CSV Dataset. This avoids wasting resources at run-time. </p> -</div><div class="section"><h1 id="beanshell_server">17.8 BeanShell server<a class="sectionlink" href="#beanshell_server" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="beanshell_server">16.8 BeanShell server<a class="sectionlink" href="#beanshell_server" title="Link to here">¶</a> +</h1> + <p> The BeanShell interpreter has a very useful feature - it can act as a server, which is accessible by telnet or http. </p> -<div class="clear"></div><div class="note"> + +<div class="clear"></div> +<div class="note"> There is no security. Anyone who can connect to the port can issue any BeanShell commands. These can provide unrestricted access to the JMeter application and the host. <b>Do not enable the server unless the ports are protected against access, e.g. by a firewall.</b> -</div><div class="clear"></div> + +</div> +<div class="clear"></div> + <p> If you do wish to use the server, define the following in <span class="code">jmeter.properties</span>: </p> + <pre class="source"> beanshell.server.port=9000 beanshell.server.file=../extras/startup.bsh </pre> + <p> In the above example, the server will be started, and will listen on ports <span class="code">9000</span> and <span class="code">9001</span>. Port <span class="code">9000</span> will be used for http access. Port <span class="code">9001</span> will be used for telnet access. @@ -145,12 +410,14 @@ The <span class="code">startup.bsh</span The startup file defines methods for setting and printing JMeter and system properties. This is what you should see in the JMeter console: </p> + <pre class="source"> Startup script running Startup script completed Httpd started on port: 9000 Session started on port: 9001 </pre> + <p> There is a sample script (<span class="code">extras/remote.bsh</span>) you can use to test the server. [Have a look at it to see how it works.] @@ -180,7 +447,9 @@ EXAMPLE = 9 remote.bsh ended bsh % … disconnected from server. </pre> + </p> + <p> As a practical example, assume you have a long-running JMeter test running in non-GUI mode, and you want to vary the throughput at various times during the test. @@ -188,6 +457,7 @@ The test-plan includes a Constant Throug e.g. <span class="code">${__P(throughput)}</span>. The following BeanShell commands could be used to change the test: </p> + <pre class="source"> printprop("throughput"); curr = Integer.decode(args[0]); // Start value @@ -201,24 +471,39 @@ while(curr <= end) { } printprop("throughput"); </pre> + <p>The script can be stored in a file (<span class="code">throughput.bsh</span>, say), and sent to the server using <span class="code">bshclient.jar</span>. For example: </p> + <pre class="source"> java -jar ../lib/bshclient.jar localhost 9000 throughput.bsh 70 5 100 60 </pre> -</div><div class="section"><h1 id="bsh_scripting">17.9 BeanShell scripting<a class="sectionlink" href="#bsh_scripting" title="Link to here">¶</a></h1> -<div class="clear"></div><div class="note">Since JMeter 3.1, we advise switching from BeanShell to JSR223 Test Elements (see JSR223 section below for more details), and switching from <span class="code"><a href="functions.html#__BeanShell">__Beanshell</a></span> function -to <a href="functions.html#__groovy">__groovy</a> function.</div><div class="clear"></div> -<div class="subsection"><h2 id="bsh_overview">17.9.1 Overview<a class="sectionlink" href="#bsh_overview" title="Link to here">¶</a></h2> + +</div> +<div class="section"> +<h1 id="bsh_scripting">16.9 BeanShell scripting<a class="sectionlink" href="#bsh_scripting" title="Link to here">¶</a> +</h1> + +<div class="clear"></div> +<div class="note">Since JMeter 3.1, we advise switching from BeanShell to JSR223 Test Elements (see JSR223 section below for more details), and switching from <span class="code"><a href="functions.html#__BeanShell">__Beanshell</a></span> function +to <a href="functions.html#__groovy">__groovy</a> function.</div> +<div class="clear"></div> + +<div class="subsection"> +<h2 id="bsh_overview">16.9.1 Overview<a class="sectionlink" href="#bsh_overview" title="Link to here">¶</a> +</h2> + <p> Each BeanShell test element has its own copy of the interpreter (for each thread). If the test element is repeatedly called, e.g. within a loop, then the interpreter is retained between invocations unless the "<span class="code">Reset bsh.Interpreter before each call</span>" option is selected. </p> + <p> Some long-running tests may cause the interpreter to use lots of memory; if this is the case try using the reset option. </p> + <p> You can test BeanShell scripts outside JMeter by using the command-line interpreter: <pre class="source"> @@ -230,13 +515,20 @@ $ java -cp bsh-xxx.jar bsh.Interpreter bsh% source("file.bsh"); bsh% exit(); // or use EOF key (e.g. ^Z or ^D) </pre> + </p> + </div> -<div class="subsection"><h2 id="bsh_variables">17.9.2 Sharing Variables<a class="sectionlink" href="#bsh_variables" title="Link to here">¶</a></h2> + +<div class="subsection"> +<h2 id="bsh_variables">16.9.2 Sharing Variables<a class="sectionlink" href="#bsh_variables" title="Link to here">¶</a> +</h2> + <p> Variables can be defined in startup (initialisation) scripts. These will be retained across invocations of the test element, unless the reset option is used. </p> + <p> Scripts can also access JMeter variables using the <span class="code">get()</span> and <span class="code">put()</span> methods of the "<span class="code">vars</span>" variable, for example: @@ -246,6 +538,7 @@ The <span class="code">get()</span> and but there are also <span class="code">getObject()</span> and <span class="code">putObject()</span> methods which can be used for arbitrary objects. JMeter variables are local to a thread, but can be used by all test elements (not just Beanshell). </p> + <p> If you need to share variables between threads, then JMeter properties can be used: <pre class="source"> @@ -255,6 +548,7 @@ JMeterUtils.setProperty("name", "value") </pre> The sample <span class="code">.bshrc</span> files contain sample definitions of <span class="code">getprop()</span> and <span class="code">setprop()</span> methods. </p> + <p> Another possible method of sharing variables is to use the "<span class="code">bsh.shared</span>" shared namespace. For example: @@ -268,19 +562,27 @@ bsh.shared.myObj.process(); Rather than creating the object in the test element, it can be created in the startup file defined by the JMeter property "<span class="code">beanshell.init.file</span>". This is only processed once. </p> + +</div> + </div> -</div><div class="section"><h1 id="developing_scripts">17.10 Developing script functions in Groovy or Jexl3 etc.<a class="sectionlink" href="#developing_scripts" title="Link to here">¶</a></h1> +<div class="section"> +<h1 id="developing_scripts">16.10 Developing script functions in Groovy or Jexl3 etc.<a class="sectionlink" href="#developing_scripts" title="Link to here">¶</a> +</h1> + <p> It's quite hard to write and test scripts as functions. However, JMeter has the JSR223 samplers which can be used instead with any language supporting it. We advise using <a href="http://www.groovy-lang.org/";>Apache Groovy</a> or any language that supports the <span class="code"><a href="https://docs.oracle.com/javase/8/docs/api/javax/script/Compilable.html";>Compilable</a></span> interface of JSR223. </p> + <p> Create a simple Test Plan containing the JSR223 Sampler and Tree View Listener. Code the script in the sampler script pane, and test it by running the test. If there are any errors, these will show up in the Tree View and <span class="code">jmeter.log</span> file. Also the result of running the script will show up as the response. </p> + <p> Once the script is working properly, it can be stored as a variable on the Test Plan. The script variable can then be used to create the function call. @@ -289,16 +591,23 @@ The function call can then be coded as < There is no need to escape any commas in the script, because the function call is parsed before the variable's value is interpolated. </p> -</div><div class="section"><h1 id="parameterising_tests">17.11 Parameterising tests<a class="sectionlink" href="#parameterising_tests" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="parameterising_tests">16.11 Parameterising tests<a class="sectionlink" href="#parameterising_tests" title="Link to here">¶</a> +</h1> + <p> Often it is useful to be able to re-run the same test with different settings. For example, changing the number of threads or loops, or changing a hostname. </p> + <p> One way to do this is to define a set of variables on the Test Plan, and then use those variables in the test elements. For example, one could define the variable <span class="code">LOOPS=10</span>, and refer to that in the Thread Group as <span class="code">${LOOPS}</span>. To run the test with 20 loops, just change the value of the <span class="code">LOOPS</span> variable on the Test Plan. </p> + <p> This quickly becomes tedious if you want to run lots of tests in non-GUI mode. One solution to this is to define the Test Plan variable in terms of a property, @@ -310,61 +619,131 @@ If there are a lot of properties that ne then one way to achieve this is to use a set of property files. The appropriate property file can be passed in to JMeter using the <span class="code">-q</span> command-line option. </p> -</div><div class="section"><h1 id="jsr223">17.12 JSR223 Elements<a class="sectionlink" href="#jsr223" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="jsr223">16.12 JSR223 Elements<a class="sectionlink" href="#jsr223" title="Link to here">¶</a> +</h1> + <p> For intensive load testing, the recommended scripting language is one whose ScriptingEngine implements the <span class="code"><a href="https://docs.oracle.com/javase/8/docs/api/javax/script/Compilable.html";>Compilable</a></span> interface. Groovy scripting engine implements <span class="code"><a href="https://docs.oracle.com/javase/8/docs/api/javax/script/Compilable.html";>Compilable</a></span>. However neither Beanshell nor Javascript do so as of release date of JMeter 3.1, so it is recommended to avoid them for intensive load testing. -<div class="clear"></div><div class="note">Note: Beanshell implements the <span class="code"><a href="https://docs.oracle.com/javase/8/docs/api/javax/script/Compilable.html";>Compilable</a></span> interface but it has not been coded - the method just throws an Exception. -JMeter has an explicit work-round for this bug.</div><div class="clear"></div> +<div class="clear"></div> +<div class="note">Note: Beanshell implements the <span class="code"><a href="https://docs.oracle.com/javase/8/docs/api/javax/script/Compilable.html";>Compilable</a></span> interface but it has not been coded - the method just throws an Exception. +JMeter has an explicit work-round for this bug.</div> +<div class="clear"></div> When using JSR 223 elements, it is advised to check <span class="code">Cache compiled script if available</span> property to ensure the script compilation is cached if underlying language supports it. In this case, ensure the script does not use any variable using <span class="code">${varName}</span> as caching would take only first value of <span class="code">${varName}</span>. Instead use : <pre class="source"> vars.get("varName") </pre> + </p> + <p> You can also pass them as Parameters to the script and use them this way. </p> -</div><div class="section"><h1 id="sharing_variables">17.13 Sharing variables between threads and thread groups<a class="sectionlink" href="#sharing_variables" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="sharing_variables">16.13 Sharing variables between threads and thread groups<a class="sectionlink" href="#sharing_variables" title="Link to here">¶</a> +</h1> + <p> Variables are local to a thread; a variable set in one thread cannot be read in another. This is by design. For variables that can be determined before a test starts, see <a href="#parameterising_tests">Parameterising Tests</a> (above). If the value is not known until the test starts, there are various options: <ul> + <li>Store the variable as a property - properties are global to the JMeter instance</li> + <li>Write variables to a file and re-read them.</li> -<li>Use the <span class="code">bsh.shared</span> namespace - see <a href="#bsh_variables">above</a></li> + +<li>Use the <span class="code">bsh.shared</span> namespace - see <a href="#bsh_variables">above</a> +</li> + <li>Write your own Java classes</li> + </ul> + </p> -</div><div class="section"><h1 id="properties">17.14 Managing properties<a class="sectionlink" href="#properties" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="properties">16.14 Managing properties<a class="sectionlink" href="#properties" title="Link to here">¶</a> +</h1> + <p>When you need to modify jmeter properties, ensure you don't modify <span class="code">jmeter.properties</span> file, <b>instead copy the property from <span class="code">jmeter.properties</span> and modify its value in <span class="code">user.properties</span> file</b>.<br> Doing so will ease you migration to the next version of JMeter. <br> Note that in the documentation <span class="code">jmeter.properties</span> is frequently mentioned but this should be understood as "Copy from <span class="code">jmeter.properties</span> to <span class="code">user.properties</span> the property you want to modify and do so in the latter file".</p> -<div class="clear"></div><div class="note"><span class="code">user.properties</span> file supersedes the properties defined in <span class="code">jmeter.properties</span></div><div class="clear"></div> -</div><div class="section"><h1 id="deprecation">17.15 Deprecated elements<a class="sectionlink" href="#deprecation" title="Link to here">¶</a></h1> + +<div class="clear"></div> +<div class="note"> +<span class="code">user.properties</span> file supersedes the properties defined in <span class="code">jmeter.properties</span> +</div> +<div class="clear"></div> + +</div> +<div class="section"> +<h1 id="deprecation">16.15 Deprecated elements<a class="sectionlink" href="#deprecation" title="Link to here">¶</a> +</h1> + <p>It is advised not to use deprecated elements (marked as such in <a href="../changes.html">changes list</a> and in <a href="./component_reference.html">component reference</a>) and to migrate to new advised elements if available or new way of doing the same thing. <br> Deprecated elements are removed from the menu in version N but can be enabled for migration by modifying <span class="code">not_in_menu</span> property in <span class="code">user.properties</span> file and removing the full class name -of the element from there.<br></p> -<div class="clear"></div><div class="note">Please note that deprecated elements in version N will be removed definitely in version N+1, so ensure you stop using them as soon as possible.</div><div class="clear"></div> -</div><ul class="pagelinks"><li><a href="realtime-results.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="boss.html">Next ></a></li></ul><div class="share-links"> +of the element from there.<br> +</p> + +<div class="clear"></div> +<div class="note">Please note that deprecated elements in version N will be removed definitely in version N+1, so ensure you stop using them as soon as possible.</div> +<div class="clear"></div> + +</div> +<ul class="pagelinks"> +<li> +<a href="realtime-results.html">< Prev</a> +</li> +<li> +<a href="../index.html">Index</a> +</li> +<li> +<a href="boss.html">Next ></a> +</li> +</ul> +<div class="share-links"> Share this page: - <ul><li class="fb"><a data-social-url="https://facebook.com/sharer/sharer.php?u="; title="Share on facebook"><i class="fa fa-facebook" aria-hidden="true"></i>share</a></li><li class="twitter"><a data-social-url="https://twitter.com/intent/tweet?url="; title="Tweet on twitter"><i class="fa fa-twitter" aria-hidden="true"></i>tweet</a></li><li class="gplus"><a data-social-url="https://plus.google.com/share?url="; title="Share on Google+"><i class="fa fa-google-plus" aria-hidden="true"></i>share</a></li></ul></div></div><div class="footer"><div class="copyright"> + <ul> +<li class="fb"> +<a data-social-url="https://facebook.com/sharer/sharer.php?u="; title="Share on facebook"><i class="fa fa-facebook" aria-hidden="true"></i>share</a> +</li> +<li class="twitter"> +<a data-social-url="https://twitter.com/intent/tweet?url="; title="Tweet on twitter"><i class="fa fa-twitter" aria-hidden="true"></i>tweet</a> +</li> +<li class="gplus"> +<a data-social-url="https://plus.google.com/share?url="; title="Share on Google+"><i class="fa fa-google-plus" aria-hidden="true"></i>share</a> +</li> +</ul> +</div> +</div> +<div class="footer"> +<div class="copyright"> Copyright © 1999 – 2017 , Apache Software Foundation - </div><div class="trademarks">Apache, Apache JMeter, JMeter, the Apache + </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><script>(function(){ + </div> +</div> +<script>(function(){ // fill in the current location into social links on this page. "use strict"; var as = document.getElementsByTagName('a'); @@ -378,4 +757,6 @@ of the element from there.<br></p> as[i].href = href + encodeURIComponent(loc); } } - })();</script></body></html> \ No newline at end of file + })();</script> +</body> +</html>
Modified: jmeter/trunk/docs/usermanual/boss.html URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/boss.html?rev=1808646&r1=1808645&r2=1808646&view=diff ============================================================================== --- jmeter/trunk/docs/usermanual/boss.html (original) +++ jmeter/trunk/docs/usermanual/boss.html Sun Sep 17 18:22:16 2017 @@ -1,38 +1,246 @@ <!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 +<html lang="en"> +<head> +<META http-equiv="Content-Type" content="text/html; charset=iso-8859-15"> +<title>Apache JMeter - - User's Manual: My boss wants me to …</title><meta name="author" value="JMeter developers"><meta name="email" value="d...@jmeter.apache.org"><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 href="https://maxcdn.bootstrapcdn.com/font-awesome/4.6.1/css/font-awesome.min.css"; 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"><!-- + User's Manual: My boss wants me to …</title> +<meta name="author" value="JMeter developers"> +<meta name="email" value="d...@jmeter.apache.org"> +<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 href="https://maxcdn.bootstrapcdn.com/font-awesome/4.6.1/css/font-awesome.min.css"; 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="asf-logo logo" src="../images/asf-logo.svg" alt="Logo ASF"></a></div><!-- + --> +<div> +<a href="http://www.apache.org";><img title="Apache Software Foundation" class="asf-logo 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"><a href="http://www.apache.org/events/current-event.html";><img src="http://www.apache.org/events/current-event-234x60.png"; alt="Current Apache event teaser"></a><div class="clear"></div></div></div><div class="nav"><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="../changes.html">Release Notes</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Documentation</div><ul><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="../usermanual/properties_reference.html">Properties Reference</a></li><li><a href="../changes_history.html">Change History</a></li><li><a href="../api/index.html">Javadocs</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</div><ul><li><a href="../usermanual/jmeter_distributed_testing_step_by_step.html">Distributed Testing</a></li><li><a href="../usermanual/jmeter_proxy_step_by_step.html">Recording Tests</a></li><li><a href="../usermanual/junitsampler_tutorial.html">JUnit Sampler</a></li><li><a href="../usermanual/jmeter_accesslog_sampler_step_by_step.html">Access Log Sampler</a></li><li><a href="../usermanual/jmeter_tutorial.html">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"><div class="social-media"><ul class="social-media-links"><li class="twitter"><a href="https://twitter.com/ApacheJMeter"; title="Follow us on Twitter"><i class="fa fa-twitter" aria-hidden="true"></i>Twitter</a></li><li class="github"><a href="https://github.com/apache/jmeter"; title="Fork us on github"><i class="fa fa-github" aria-hidden="true"></i>github</a></li></ul></div><ul class="pagelinks"><li><a href="best-practices.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="component_reference.html">Next ></a></li></ul><div class="section"><h1 id="boss">18. Help! My boss wants me to load test our application!<a class="sectionlink" href="#boss" title="Link to here">¶</a></h1> + --> +<div> +<a href="http://jmeter.apache.org/";><img class="logo" src="../images/logo.svg" alt="Apache JMeter"></a> +</div> +<div class="banner"> +<a href="http://www.apache.org/events/current-event.html";><img src="http://www.apache.org/events/current-event-234x60.png"; alt="Current Apache event teaser"></a> +<div class="clear"></div> +</div> +</div> +<div class="nav"> +<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="../changes.html">Release Notes</a> +</li> +</ul> +</li> +</ul> +<ul class="menu"> +<li onClick="return true"> +<div class="menu-title">Documentation</div> +<ul> +<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="../usermanual/properties_reference.html">Properties Reference</a> +</li> +<li> +<a href="../changes_history.html">Change History</a> +</li> +<li> +<a href="../api/index.html">Javadocs</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</div> +<ul> +<li> +<a href="../usermanual/jmeter_distributed_testing_step_by_step.html">Distributed Testing</a> +</li> +<li> +<a href="../usermanual/jmeter_proxy_step_by_step.html">Recording Tests</a> +</li> +<li> +<a href="../usermanual/junitsampler_tutorial.html">JUnit Sampler</a> +</li> +<li> +<a href="../usermanual/jmeter_accesslog_sampler_step_by_step.html">Access Log Sampler</a> +</li> +<li> +<a href="../usermanual/jmeter_tutorial.html">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="http://www.apache.org/security/";>Security</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/";>The Apache Software Foundation (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"> +<div class="social-media"> +<ul class="social-media-links"> +<li class="twitter"> +<a href="https://twitter.com/ApacheJMeter"; title="Follow us on Twitter"><i class="fa fa-twitter" aria-hidden="true"></i>Twitter</a> +</li> +<li class="github"> +<a href="https://github.com/apache/jmeter"; title="Fork us on github"><i class="fa fa-github" aria-hidden="true"></i>github</a> +</li> +</ul> +</div> +<ul class="pagelinks"> +<li> +<a href="best-practices.html">< Prev</a> +</li> +<li> +<a href="../index.html">Index</a> +</li> +<li> +<a href="component_reference.html">Next ></a> +</li> +</ul> +<div class="section"> +<h1 id="boss">17. Help! My boss wants me to load test our application!<a class="sectionlink" href="#boss" title="Link to here">¶</a> +</h1> + <p>This is a fairly open-ended proposition. There are a number of questions to be asked first, and additionally a number of resources that will be needed. You will need some hardware to run the benchmarks/load-tests from. A number of tools will prove useful. There are a number of products to consider. And finally, why is Java a good choice to implement a load-testing/Benchmarking product. </p> -<div class="subsection"><h2 id="questions">18.1 Questions to ask<a class="sectionlink" href="#questions" title="Link to here">¶</a></h2> + +<div class="subsection"> +<h2 id="questions">17.1 Questions to ask<a class="sectionlink" href="#questions" title="Link to here">¶</a> +</h2> + <p>What is our anticipated average number of users (normal load)? </p> + <p>What is our anticipated peak number of users? </p> + <p>When is a good time to load-test our application (i.e. off-hours or week-ends), bearing in mind that this may very well crash one or more of our servers? </p> + <p>Does our application have state? If so, how does our application manage it (cookies, session-rewriting, or some other method)? </p> + <p>What is the testing intended to achieve?</p> + </div> -<div class="subsection"><h2 id="resources">18.2 Resources<a class="sectionlink" href="#resources" title="Link to here">¶</a></h2> + +<div class="subsection"> +<h2 id="resources">17.2 Resources<a class="sectionlink" href="#resources" title="Link to here">¶</a> +</h2> + <p>The following resources will prove very helpful. Bear in mind that if you cannot locate these resources, <b>you</b> will become these resources. As you already have your work cut out for you, it is worth knowing who the following people are, so that you can ask them for help if you need it. </p> - <div class="subsection"><h2 id="network">18.2.1 Network<a class="sectionlink" href="#network" title="Link to here">¶</a></h2> - <p>Who knows our network topology? If you run into any firewall or + +<div class="subsection"> +<h2 id="network">17.2.1 Network<a class="sectionlink" href="#network" title="Link to here">¶</a> +</h2> + +<p>Who knows our network topology? If you run into any firewall or proxy issues, this will become very important. As well, a private testing network (which will therefore have very low network latency) would be a very nice thing. Knowing who can set one up for you @@ -40,90 +248,140 @@ people are, so that you can ask them for application doesn't scale as expected, who can add additional hardware? </p> - </div> - <div class="subsection"><h2 id="application">18.2.2 Application<a class="sectionlink" href="#application" title="Link to here">¶</a></h2> - <p>Who knows how our application functions? The normal sequence is + +</div> + +<div class="subsection"> +<h2 id="application">17.2.2 Application<a class="sectionlink" href="#application" title="Link to here">¶</a> +</h2> + +<p>Who knows how our application functions? The normal sequence is <ul> - <li>test (low-volume - can we benchmark our application?)</li> - <li>benchmark (the average number of users)</li> - <li>load-test (the maximum number of users)</li> - <li>test destructively (what is our hard limit?)</li> - </ul> + +<li>test (low-volume - can we benchmark our application?)</li> + +<li>benchmark (the average number of users)</li> + +<li>load-test (the maximum number of users)</li> + +<li>test destructively (what is our hard limit?)</li> + +</ul> The <b>test</b> process may progress from black-box testing to white-box testing (the difference is that the first requires no knowledge of the application [it is treated as a "black box"] while the second requires some knowledge of the application). It is not uncommon to discover problems with the application during this process, so be prepared to defend your work.</p> - </div> + +</div> + </div> -<div class="subsection"><h2 id="platform">18.3 What platform should I use to run the benchmarks/load-tests?<a class="sectionlink" href="#platform" title="Link to here">¶</a></h2> + +<div class="subsection"> +<h2 id="platform">17.3 What platform should I use to run the benchmarks/load-tests?<a class="sectionlink" href="#platform" title="Link to here">¶</a> +</h2> + <p>This should be a widely-used piece of hardware, with a standard (i.e. vanilla) software installation. Remember, if you publish your results, the first thing your clients will do is hire a graduate student to verify them. You might as well make it as easy for this person as you possibly can. </p> + <p>For Windows, Windows XP Professional should be a minimum (the others do not multi-thread past 50-60 connections, and you probably anticipate more users than that). </p> + <p>Good free platforms include the linuxes, the BSDs, and Solaris Intel. If you have a little more money, there are commercial linuxes. This may be worth it if you need the support. </p> + <p> For non-Windows platforms, investigate "<span class="code">ulimit -n unlimited</span>" with a view to including it in your user account startup scripts (<span class="code">.bashrc</span> or <span class="code">.cshrc</span> scripts for the testing account). </p> + <p> Also note that some Linux/Unix editions are intended for server use. These generally have minimal or no GUI support. Such OSes should be OK for running JMeter in non-GUI mode, but JMeter GUI mode probably won't work unless you install a minimal GUI environment. </p> + <p>As you progress to larger-scale benchmarks/load-tests, this platform will become the limiting factor. So it's worth using the best hardware and software that you have available. Remember to include the hardware/software configuration in your published benchmarks. </p> -<p><b>When you need a lot of machines or want to test the network latency, Cloud can help you.</b> + +<p> +<b>When you need a lot of machines or want to test the network latency, Cloud can help you.</b> JMeter can easily be installed on Cloud instances as it runs on nearly any architecture available in the Cloud. JMeter is also supported within Commercial Cloud PAAS if you don't want to manage it yourself. </p> + <p>Don't forget JMeter batch (NON-GUI) mode. This mode should be used during load testing for many reasons: <ul> + <li>If you have a powerful server that supports Java but perhaps does not have a fast graphics implementation, or where you need to login remotely.</li> + <li>Batch (non-GUI) mode can reduce the network traffic compared with using a remote display or client-server mode.</li> + <li>Java AWT Thread used for GUI mode can alter injection behaviour by blocking sometimes</li> + </ul> The batch log file can then be loaded into JMeter on a workstation for analysis, or you can use CSV output and import the data into a spreadsheet.</p> -<div class="clear"></div><div class="note">Remember GUI mode is for Script creation and debugging, not for load testing</div><div class="clear"></div> + +<div class="clear"></div> +<div class="note">Remember GUI mode is for Script creation and debugging, not for load testing</div> +<div class="clear"></div> + </div> -<div class="subsection"><h2 id="tools">18.4 Tools<a class="sectionlink" href="#tools" title="Link to here">¶</a></h2> + +<div class="subsection"> +<h2 id="tools">17.4 Tools<a class="sectionlink" href="#tools" title="Link to here">¶</a> +</h2> + <p>The following tools will all prove useful. It is definitely worthwhile to become familiar with them. This should include trying them out, and reading the appropriate documentation (man-pages, info-files, application --help messages, and any supplied documentation). </p> - <div class="subsection"><h2 id="ping">18.4.1 ping<a class="sectionlink" href="#ping" title="Link to here">¶</a></h2> - <p> + +<div class="subsection"> +<h2 id="ping">17.4.1 ping<a class="sectionlink" href="#ping" title="Link to here">¶</a> +</h2> + +<p> This can be used to establish whether or not you can reach your target site. Options can be specified so that '<span class="code">ping</span>' provides the same type of route reporting as '<span class="code">traceroute</span>'. </p> - </div> - <div class="subsection"><h2 id="dig">18.4.2 nslookup/dig<a class="sectionlink" href="#dig" title="Link to here">¶</a></h2> - <p> + +</div> + +<div class="subsection"> +<h2 id="dig">17.4.2 nslookup/dig<a class="sectionlink" href="#dig" title="Link to here">¶</a> +</h2> + +<p> While the <b>user</b> will normally use a human-readable internet address, <b>you</b> may wish to avoid the overhead of DNS lookups when performing benchmarking/load-testing. These can be used to determine the unique address (dotted quad) of your target site. </p> - </div> - <div class="subsection"><h2 id="traceroute">18.4.3 traceroute<a class="sectionlink" href="#traceroute" title="Link to here">¶</a></h2> - <p> + +</div> + +<div class="subsection"> +<h2 id="traceroute">17.4.3 traceroute<a class="sectionlink" href="#traceroute" title="Link to here">¶</a> +</h2> + +<p> If you cannot "<span class="code">ping</span>" your target site, this may be used to determine the problem (possibly a firewall or a proxy). It can also be used to estimate the overall network latency (running locally should give @@ -131,24 +389,43 @@ and any supplied documentation). be running over a possibly busy internet). Generally, the fewer hops the better. </p> - </div> + </div> -<div class="subsection"><h2 id="plugins">18.5 How can I enhance JMeter?<a class="sectionlink" href="#plugins" title="Link to here">¶</a></h2> + +</div> + +<div class="subsection"> +<h2 id="plugins">17.5 How can I enhance JMeter?<a class="sectionlink" href="#plugins" title="Link to here">¶</a> +</h2> + <p>There a lot of open-source and commercial providers who provide JMeter plugins or other resources for use with JMeter. Some of these are listed on the JMeter Wiki. They are listed under several categories: <ul> -<li><a href="http://wiki.apache.org/jmeter/JMeterPlugins";>JMeterPlugins</a> - plugins for extending JMeter</li> -<li><a href="http://wiki.apache.org/jmeter/JMeterAddons";>JMeterAddons</a> - addons for use with JMeter, e.g. plugins for browsers, Maven and Jenkins.</li> -<li><a href="http://wiki.apache.org/jmeter/JMeterServices";>JMeterServices</a> - 3<sup>rd</sup> party services, e.g. cloud-based JMeter</li> + +<li> +<a href="http://wiki.apache.org/jmeter/JMeterPlugins";>JMeterPlugins</a> - plugins for extending JMeter</li> + +<li> +<a href="http://wiki.apache.org/jmeter/JMeterAddons";>JMeterAddons</a> - addons for use with JMeter, e.g. plugins for browsers, Maven and Jenkins.</li> + +<li> +<a href="http://wiki.apache.org/jmeter/JMeterServices";>JMeterServices</a> - 3<sup>rd</sup> party services, e.g. cloud-based JMeter</li> + </ul> Note that appearance of these on the Wiki does not imply any endorsement by the Apache JMeter project. Any requests for support should be directed to the relevant supplier. </p> + </div> -<div class="subsection"><h2 id="java">18.6 Why Java?<a class="sectionlink" href="#java" title="Link to here">¶</a></h2> + +<div class="subsection"> +<h2 id="java">17.6 Why Java?<a class="sectionlink" href="#java" title="Link to here">¶</a> +</h2> + <p>Why not Perl or C? </p> + <p>Well, Perl might be a very good choice except that the Benchmark package seems to give fairly fuzzy results. Also, simulating multiple users with Perl is a tricky proposition (multiple connections can be simulated by forking @@ -157,29 +434,62 @@ be processes). However, the Perl communi someone has already written something that seems useful, this could be a very good solution. </p> + <p>C, of course, is a very good choice (check out the Apache <span class="code">ab</span> tool). But be prepared to write all of the custom networking, threading, and state management code that you will need to benchmark your application. </p> + <p>Java gives you (for free) the custom networking, threading, and state management code that you will need to benchmark your application. Java is aware of HTTP, FTP, and HTTPS - as well as RMI, IIOP, and JDBC (not to mention cookies, URL-encoding, and URL-rewriting). In addition Java gives you automatic garbage-collection, and byte-code level security. </p> + +</div> + </div> -</div><ul class="pagelinks"><li><a href="best-practices.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="component_reference.html">Next ></a></li></ul><div class="share-links"> +<ul class="pagelinks"> +<li> +<a href="best-practices.html">< Prev</a> +</li> +<li> +<a href="../index.html">Index</a> +</li> +<li> +<a href="component_reference.html">Next ></a> +</li> +</ul> +<div class="share-links"> Share this page: - <ul><li class="fb"><a data-social-url="https://facebook.com/sharer/sharer.php?u="; title="Share on facebook"><i class="fa fa-facebook" aria-hidden="true"></i>share</a></li><li class="twitter"><a data-social-url="https://twitter.com/intent/tweet?url="; title="Tweet on twitter"><i class="fa fa-twitter" aria-hidden="true"></i>tweet</a></li><li class="gplus"><a data-social-url="https://plus.google.com/share?url="; title="Share on Google+"><i class="fa fa-google-plus" aria-hidden="true"></i>share</a></li></ul></div></div><div class="footer"><div class="copyright"> + <ul> +<li class="fb"> +<a data-social-url="https://facebook.com/sharer/sharer.php?u="; title="Share on facebook"><i class="fa fa-facebook" aria-hidden="true"></i>share</a> +</li> +<li class="twitter"> +<a data-social-url="https://twitter.com/intent/tweet?url="; title="Tweet on twitter"><i class="fa fa-twitter" aria-hidden="true"></i>tweet</a> +</li> +<li class="gplus"> +<a data-social-url="https://plus.google.com/share?url="; title="Share on Google+"><i class="fa fa-google-plus" aria-hidden="true"></i>share</a> +</li> +</ul> +</div> +</div> +<div class="footer"> +<div class="copyright"> Copyright © 1999 – 2017 , Apache Software Foundation - </div><div class="trademarks">Apache, Apache JMeter, JMeter, the Apache + </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><script>(function(){ + </div> +</div> +<script>(function(){ // fill in the current location into social links on this page. "use strict"; var as = document.getElementsByTagName('a'); @@ -193,4 +503,6 @@ garbage-collection, and byte-code level as[i].href = href + encodeURIComponent(loc); } } - })();</script></body></html> \ No newline at end of file + })();</script> +</body> +</html> Modified: jmeter/trunk/docs/usermanual/build-adv-web-test-plan.html URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/build-adv-web-test-plan.html?rev=1808646&r1=1808645&r2=1808646&view=diff ============================================================================== --- jmeter/trunk/docs/usermanual/build-adv-web-test-plan.html (original) +++ jmeter/trunk/docs/usermanual/build-adv-web-test-plan.html Sun Sep 17 18:22:16 2017 @@ -1,18 +1,214 @@ <!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 +<html lang="en"> +<head> +<META http-equiv="Content-Type" content="text/html; charset=iso-8859-15"> +<title>Apache JMeter - - User's Manual: Building an Advanced Web 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 href="https://maxcdn.bootstrapcdn.com/font-awesome/4.6.1/css/font-awesome.min.css"; 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"><!-- + User's Manual: Building an Advanced Web 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 href="https://maxcdn.bootstrapcdn.com/font-awesome/4.6.1/css/font-awesome.min.css"; 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="asf-logo logo" src="../images/asf-logo.svg" alt="Logo ASF"></a></div><!-- + --> +<div> +<a href="http://www.apache.org";><img title="Apache Software Foundation" class="asf-logo 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"><a href="http://www.apache.org/events/current-event.html";><img src="http://www.apache.org/events/current-event-234x60.png"; alt="Current Apache event teaser"></a><div class="clear"></div></div></div><div class="nav"><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="../changes.html">Release Notes</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Documentation</div><ul><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="../usermanual/properties_reference.html">Properties Reference</a></li><li><a href="../changes_history.html">Change History</a></li><li><a href="../api/index.html">Javadocs</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</div><ul><li><a href="../usermanual/jmeter_distributed_testing_step_by_step.html">Distributed Testing</a></li><li><a href="../usermanual/jmeter_proxy_step_by_step.html">Recording Tests</a></li><li><a href="../usermanual/junitsampler_tutorial.html">JUnit Sampler</a></li><li><a href="../usermanual/jmeter_accesslog_sampler_step_by_step.html">Access Log Sampler</a></li><li><a href="../usermanual/jmeter_tutorial.html">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"><div class="social-media"><ul class="social-media-links"><li class="twitter"><a href="https://twitter.com/ApacheJMeter"; title="Follow us on Twitter"><i class="fa fa-twitter" aria-hidden="true"></i>Twitter</a></li><li class="github"><a href="https://github.com/apache/jmeter"; title="Fork us on github"><i class="fa fa-github" aria-hidden="true"></i>github</a></li></ul></div><ul class="pagelinks"><li><a href="build-web-test-plan.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="build-db-test-plan.html">Next ></a></li></ul><div class="section"><h1 id="building">5. Building an Advanced Web Test Plan<a class="sectionlink" href="#building" title="Link to here">¶</a></h1> + --> +<div> +<a href="http://jmeter.apache.org/";><img class="logo" src="../images/logo.svg" alt="Apache JMeter"></a> +</div> +<div class="banner"> +<a href="http://www.apache.org/events/current-event.html";><img src="http://www.apache.org/events/current-event-234x60.png"; alt="Current Apache event teaser"></a> +<div class="clear"></div> +</div> +</div> +<div class="nav"> +<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="../changes.html">Release Notes</a> +</li> +</ul> +</li> +</ul> +<ul class="menu"> +<li onClick="return true"> +<div class="menu-title">Documentation</div> +<ul> +<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="../usermanual/properties_reference.html">Properties Reference</a> +</li> +<li> +<a href="../changes_history.html">Change History</a> +</li> +<li> +<a href="../api/index.html">Javadocs</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</div> +<ul> +<li> +<a href="../usermanual/jmeter_distributed_testing_step_by_step.html">Distributed Testing</a> +</li> +<li> +<a href="../usermanual/jmeter_proxy_step_by_step.html">Recording Tests</a> +</li> +<li> +<a href="../usermanual/junitsampler_tutorial.html">JUnit Sampler</a> +</li> +<li> +<a href="../usermanual/jmeter_accesslog_sampler_step_by_step.html">Access Log Sampler</a> +</li> +<li> +<a href="../usermanual/jmeter_tutorial.html">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="http://www.apache.org/security/";>Security</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/";>The Apache Software Foundation (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"> +<div class="social-media"> +<ul class="social-media-links"> +<li class="twitter"> +<a href="https://twitter.com/ApacheJMeter"; title="Follow us on Twitter"><i class="fa fa-twitter" aria-hidden="true"></i>Twitter</a> +</li> +<li class="github"> +<a href="https://github.com/apache/jmeter"; title="Fork us on github"><i class="fa fa-github" aria-hidden="true"></i>github</a> +</li> +</ul> +</div> +<ul class="pagelinks"> +<li> +<a href="build-web-test-plan.html">< Prev</a> +</li> +<li> +<a href="../index.html">Index</a> +</li> +<li> +<a href="build-db-test-plan.html">Next ></a> +</li> +</ul> +<div class="section"> +<h1 id="building">5. Building an Advanced Web Test Plan<a class="sectionlink" href="#building" title="Link to here">¶</a> +</h1> + <p>In this section, you will learn how to create advanced <a href="build-test-plan.html">Test Plans</a> to test a Web site.</p> + <p>For an example of a basic Test Plan, see -<a href="build-web-test-plan.html">Building a Web Test Plan</a>.</p></div><div class="section"><h1 id="session_url_rewriting">5.1 Handling User Sessions With URL Rewriting<a class="sectionlink" href="#session_url_rewriting" title="Link to here">¶</a></h1> +<a href="build-web-test-plan.html">Building a Web Test Plan</a>.</p> +</div> +<div class="section"> +<h1 id="session_url_rewriting">5.1 Handling User Sessions With URL Rewriting<a class="sectionlink" href="#session_url_rewriting" title="Link to here">¶</a> +</h1> + <p>If your web application uses URL rewriting rather than cookies to save session information, then you'll need to do a bit of extra work to test your site.</p> + <p>To respond correctly to URL rewriting, JMeter needs to parse the HTML received from the server and retrieve the unique session ID. Use the appropriate <a href="../usermanual/component_reference.html#HTTP_URL_Re-writing_Modifier">HTTP URL Re-writing Modifier</a> to accomplish this. Simply enter the name of your session ID parameter into the modifier, and it @@ -21,37 +217,87 @@ If "Cache Session Id?" is checked, then and will be used if the previous HTTP sample does not contain a session id. </p> -<div class="example"><div class="title">URL Rewriting Example<a class="sectionlink" href="#url_rewriting_example" title="Link to here">¶</a></div> + +<div class="example"> +<div class="title">URL Rewriting Example<a class="sectionlink" href="#url_rewriting_example" title="Link to here">¶</a> +</div> + <p>Download <a href="../demos/URLRewritingExample.jmx">this example</a>. In Figure 1 is shown a test plan using URL rewriting. Note that the URL Re-writing modifier is added to the SimpleController, thus assuring that it will only affect requests under that SimpleController.</p> -<figure><a href="../images/screenshots/url_rewrite_example_a.png"><img src="../images/screenshots/url_rewrite_example_a.png" width="" height="" alt="Figure 1 - Test Tree"></a><figcaption>Figure 1 - Test Tree</figcaption></figure> + +<figure> +<a href="../images/screenshots/url_rewrite_example_a.png"><img src="../images/screenshots/url_rewrite_example_a.png" width="" height="" alt="Figure 1 - Test Tree"></a> +<figcaption>Figure 1 - Test Tree</figcaption> +</figure> + <p>In Figure 2, we see the URL Re-writing modifier GUI, which just has a field for the user to specify the name of the session ID parameter. There is also a checkbox for indicating that the session ID should be part of the path (separated by a ";"), rather than a request parameter</p> -<figure><a href="../images/screenshots/url_rewrite_example_b.png"><img src="../images/screenshots/url_rewrite_example_b.png" width="" height="" alt="Figure 2 - Request parameters"></a><figcaption>Figure 2 - Request parameters</figcaption></figure> + +<figure> +<a href="../images/screenshots/url_rewrite_example_b.png"><img src="../images/screenshots/url_rewrite_example_b.png" width="" height="" alt="Figure 2 - Request parameters"></a> +<figcaption>Figure 2 - Request parameters</figcaption> +</figure> + </div> -</div><div class="section"><h1 id="header_manager">5.2 Using a Header Manager<a class="sectionlink" href="#header_manager" title="Link to here">¶</a></h1> + +</div> +<div class="section"> +<h1 id="header_manager">5.2 Using a Header Manager<a class="sectionlink" href="#header_manager" title="Link to here">¶</a> +</h1> + <p>The <a href="../usermanual/component_reference.html#HTTP_Header_Manager">HTTP Header Manager</a> lets you customize what information JMeter sends in the HTTP request header. This header includes properties like "User-Agent", "Pragma", "Referer", etc.</p> + <p>The <a href="../usermanual/component_reference.html#HTTP_Header_Manager">HTTP Header Manager</a>, like the <a href="../usermanual/component_reference.html#HTTP_Cookie_Manager">HTTP Cookie Manager</a>, should probably be added at the Thread Group level, unless for some reason you wish to specify different headers for the different <a href="../usermanual/component_reference.html#HTTP_Request">HTTP Request</a> objects in your test.</p> -</div><ul class="pagelinks"><li><a href="build-web-test-plan.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="build-db-test-plan.html">Next ></a></li></ul><div class="share-links"> + +</div> +<ul class="pagelinks"> +<li> +<a href="build-web-test-plan.html">< Prev</a> +</li> +<li> +<a href="../index.html">Index</a> +</li> +<li> +<a href="build-db-test-plan.html">Next ></a> +</li> +</ul> +<div class="share-links"> Share this page: - <ul><li class="fb"><a data-social-url="https://facebook.com/sharer/sharer.php?u="; title="Share on facebook"><i class="fa fa-facebook" aria-hidden="true"></i>share</a></li><li class="twitter"><a data-social-url="https://twitter.com/intent/tweet?url="; title="Tweet on twitter"><i class="fa fa-twitter" aria-hidden="true"></i>tweet</a></li><li class="gplus"><a data-social-url="https://plus.google.com/share?url="; title="Share on Google+"><i class="fa fa-google-plus" aria-hidden="true"></i>share</a></li></ul></div></div><div class="footer"><div class="copyright"> + <ul> +<li class="fb"> +<a data-social-url="https://facebook.com/sharer/sharer.php?u="; title="Share on facebook"><i class="fa fa-facebook" aria-hidden="true"></i>share</a> +</li> +<li class="twitter"> +<a data-social-url="https://twitter.com/intent/tweet?url="; title="Tweet on twitter"><i class="fa fa-twitter" aria-hidden="true"></i>tweet</a> +</li> +<li class="gplus"> +<a data-social-url="https://plus.google.com/share?url="; title="Share on Google+"><i class="fa fa-google-plus" aria-hidden="true"></i>share</a> +</li> +</ul> +</div> +</div> +<div class="footer"> +<div class="copyright"> Copyright © 1999 – 2017 , Apache Software Foundation - </div><div class="trademarks">Apache, Apache JMeter, JMeter, the Apache + </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><script>(function(){ + </div> +</div> +<script>(function(){ // fill in the current location into social links on this page. "use strict"; var as = document.getElementsByTagName('a'); @@ -65,4 +311,6 @@ your test.</p> as[i].href = href + encodeURIComponent(loc); } } - })();</script></body></html> \ No newline at end of file + })();</script> +</body> +</html>
![http://www.apache.org/events/current-event-234x60.png"](http://www.apache.org/events/current-event-234x60.png"){kind=link}