From commits-return-4236-apmail-jmeter-commits-archive=jmeter.apache.org@jmeter.apache.org Sun Sep 20 11:44:34 2015 Return-Path: X-Original-To: apmail-jmeter-commits-archive@minotaur.apache.org Delivered-To: apmail-jmeter-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 36F98180E5 for ; Sun, 20 Sep 2015 11:44:34 +0000 (UTC) Received: (qmail 21971 invoked by uid 500); 20 Sep 2015 11:44:34 -0000 Delivered-To: apmail-jmeter-commits-archive@jmeter.apache.org Received: (qmail 21942 invoked by uid 500); 20 Sep 2015 11:44:34 -0000 Mailing-List: contact commits-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jmeter.apache.org Delivered-To: mailing list commits@jmeter.apache.org Received: (qmail 21913 invoked by uid 99); 20 Sep 2015 11:44:34 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Sep 2015 11:44:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 8DB051A27AA for ; Sun, 20 Sep 2015 11:44:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.5 X-Spam-Level: *** X-Spam-Status: No, score=3.5 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RDNS_NONE=2.5] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id avz5dGBobW_T for ; Sun, 20 Sep 2015 11:44:25 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (unknown [209.188.14.139]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id 807A920F4B for ; Sun, 20 Sep 2015 11:44:25 +0000 (UTC) Received: from svn01-us-west.apache.org (svn.apache.org [10.41.0.6]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 0B608E022D for ; Sun, 20 Sep 2015 11:44:25 +0000 (UTC) Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id D5B4A3A0423 for ; Sun, 20 Sep 2015 11:44:24 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1704122 - /jmeter/trunk/xdocs/usermanual/component_reference.xml Date: Sun, 20 Sep 2015 11:44:24 -0000 To: commits@jmeter.apache.org From: fschumacher@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150920114424.D5B4A3A0423@svn01-us-west.apache.org> Author: fschumacher Date: Sun Sep 20 11:44:24 2015 New Revision: 1704122 URL: http://svn.apache.org/viewvc?rev=1704122&view=rev Log: Mostly markup changes. Usage of code, source and example tags. Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1704122&r1=1704121&r2=1704122&view=diff ============================================================================== --- jmeter/trunk/xdocs/usermanual/component_reference.xml (original) +++ jmeter/trunk/xdocs/usermanual/component_reference.xml Sun Sep 20 11:44:24 2015 @@ -6088,8 +6088,8 @@ The Test Plan is where the overall setti

Static variables can be defined for values that are repeated throughout a test, such as server names. -For example the variable SERVER could be defined as www.example.com, and the rest of the test plan -could refer to it as ${SERVER}. This simplifies changing the name later. +For example the variable SERVER could be defined as www.example.com, and the rest of the test plan +could refer to it as ${SERVER}. This simplifies changing the name later.

If the same variable name is reused on one of more @@ -6108,7 +6108,7 @@ Selecting Functional Testing instructs J - Response Data and Sampler Data - to all result files. This increases the resources needed to run a test, and may adversely impact JMeter performance. If more data is required for a particular sampler only, then add a Listener to it, and configure the fields as required. -[The option does not affect CSV result files, which cannot currently store such information.] +The option does not affect CSV result files, which cannot currently store such information.

Also, an option exists here to instruct JMeter to run the serially rather than in parallel.

Run tearDown Thread Groups after shutdown of main threads: @@ -6119,13 +6119,13 @@ The tearDown threads won't be run if the Test plan now provides an easy way to add classpath setting to a specific test plan. The feature is additive, meaning that you can add jar files or directories, but removing an entry requires restarting JMeter. -Note that this cannot be used to add JMeter GUI plugins, because they are processed earlier. +Note that this cannot be used to add JMeter GUI plugins, because they are processed earlier. However it can be useful for utility jars such as JDBC drivers. The jars are only added to the search path for the JMeter loader, not for the system class loader.

JMeter properties also provides an entry for loading additional classpaths. -In jmeter.properties, edit "user.classpath" or "plugin_dependency_paths" to include additional libraries. +In jmeter.properties, edit "user.classpath" or "plugin_dependency_paths" to include additional libraries. See JMeter's Classpath and Configuring JMeter for details.

@@ -6151,16 +6151,16 @@ JMeter does not interrupt samplers which Determines what happens if a sampler error occurs, either because the sample itself failed or an assertion failed. The possible choices are:
    -
  • Continue - ignore the error and continue with the test
    • -
  • Start Next Loop - ignore the error, start next loop and continue with the test
    • -
  • Stop Thread - current thread exits
    • -
  • Stop Test - the entire test is stopped at the end of any current samples.
    • -
  • Stop Test Now - the entire test is stopped abruptly. Any current samplers are interrupted if possible.
    • +
  • Continue - ignore the error and continue with the test
    • +
  • Start Next Loop - ignore the error, start next loop and continue with the test
    • +
  • Stop Thread - current thread exits
    • +
  • Stop Test - the entire test is stopped at the end of any current samples.
    • +
  • Stop Test Now - the entire test is stopped abruptly. Any current samplers are interrupted if possible.
Number of users to simulate. How long JMeter should take to get all the threads started. If there are 10 threads and a ramp-up time of 100 seconds, then each thread will begin 10 seconds after the previous thread started, for a total time of 100 seconds to get the test fully up to speed. - Number of times to perform the test case. Alternatively, "forever" can be selected causing the test to run until manually stopped. + Number of times to perform the test case. Alternatively, "forever" can be selected causing the test to run until manually stopped. If selected, threads are created only when the appropriate proportion of the ramp-up time has elapsed. This is most appropriate for tests with a ramp-up time that is significantly longer than the time to execute a single thread. @@ -6171,18 +6171,18 @@ JMeter does not interrupt samplers which If selected, enables the scheduler If the scheduler checkbox is selected, one can choose an absolute start time. When you start your test, JMeter will wait until the specified start time to begin testing. - Note: the Startup Delay field over-rides this - see below. + Note: the Startup Delay field over-rides this - see below. If the scheduler checkbox is selected, one can choose an absolute end time. When you start your test, JMeter will wait until the specified start time to begin testing, and it will stop at the specified end time. - Note: the Duration field over-rides this - see below. + Note: the Duration field over-rides this - see below. If the scheduler checkbox is selected, one can choose a relative end time. - JMeter will use this to calculate the End Time, and ignore the End Time value. + JMeter will use this to calculate the End Time, and ignore the End Time value. If the scheduler checkbox is selected, one can choose a relative startup delay. - JMeter will use this to calculate the Start Time, and ignore the Start Time value. + JMeter will use this to calculate the Start Time, and ignore the Start Time value. @@ -6190,8 +6190,8 @@ JMeter does not interrupt samplers which

The WorkBench simply provides a place to temporarily store test elements while not in use, for copy/paste purposes, or any other purpose you desire. -When you save your test plan, WorkBench items are not saved with it by default unless you check "Save Workbench" option. -Your WorkBench can be saved independently, if you like (right-click on WorkBench and choose Save).

+When you save your test plan, WorkBench items are not saved with it by default unless you check "Save Workbench" option. +Your WorkBench can be saved independently, if you like (right-click on WorkBench and choose Save).

Certain test elements are only available on the WorkBench: