jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fschumac...@apache.org
Subject [jmeter] branch master updated: Update component reference documentation for thread group option "same user on each iteration"
Date Sat, 13 Feb 2021 09:35:02 GMT
This is an automated email from the ASF dual-hosted git repository.

fschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/jmeter.git


The following commit(s) were added to refs/heads/master by this push:
     new acdb648  Update component reference documentation for thread group option "same user
on each iteration"
acdb648 is described below

commit acdb6482dd3e945e0e8acefd7109b2df3faf505c
Author: Noah <78764304+njkuzas@users.noreply.github.com>
AuthorDate: Thu Feb 11 16:00:58 2021 -0600

    Update component reference documentation for thread group option "same user on each iteration"
    
    Bugzilla Id: 65128
    Closes #643
---
 xdocs/changes.xml                        | 2 ++
 xdocs/usermanual/component_reference.xml | 6 ++++++
 2 files changed, 8 insertions(+)

diff --git a/xdocs/changes.xml b/xdocs/changes.xml
index 76c5027..96c5edf 100644
--- a/xdocs/changes.xml
+++ b/xdocs/changes.xml
@@ -117,6 +117,7 @@ Summary
 
 <ch_section>Non-functional changes</ch_section>
 <ul>
+  <li><bug>65128</bug><pr>643</pr>Add missing documentation
about <code>Same user on each iteration</code> for Thread Groups. Contributed
by njkuzas.</li>
 </ul>
 
  <!-- =================== Bug fixes =================== -->
@@ -173,6 +174,7 @@ Summary
 </p>
 <ul>
   <li>Stefan Seide (stefan at trilobyte-se.de)</li>
+  <li>njzukas (github.com/njzukas)</li>
 </ul>
 <p>We also thank bug reporters who helped us improve JMeter.</p>
 <ul>
diff --git a/xdocs/usermanual/component_reference.xml b/xdocs/usermanual/component_reference.xml
index 3183c55..14a4932 100644
--- a/xdocs/usermanual/component_reference.xml
+++ b/xdocs/usermanual/component_reference.xml
@@ -6534,6 +6534,12 @@ Behaviour can be modified with some properties by setting in <code>user.properti
                 the ramp-up time is effectively <strong>zero</strong>. For the
same reason, the tenth thread in
                 the above example will actually be started after 90 seconds and not 100 seconds.</note>
         </property>
+        <property name="Same user on each iteration" required="Yes">
+            If selected, cookie and cache data from the first sampler response are used in
subsequent requests (requires a global Cookie and Cache Manager respectively).
+            <br></br>
+            If not selected, cookie and cache data from the first sampler response are not
used in subsequent requests.
+            <note>If not selected, a new connection will be opened between iterations
which will result in increased response times and consume more resources (memory and cpu).</note>
+        </property>
         <property name="Loop Count" required="Yes, unless Infinite is selected">Number
of times to perform the test case.  Alternatively, "<code>infinite</code>" can
be selected causing the test to run until manually stopped or end of the thread lifetime is
reached.</property>
         <property name="Delay Thread creation until needed" required="Yes">
         If selected, threads are created only when the appropriate proportion of the ramp-up
time has elapsed.


Mime
View raw message