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 2c511c6 Add missing documentation about 'Same user on each iteration'
for Thread Groups.
2c511c6 is described below
commit 2c511c646f428a92c91b08e2bef25094701f5de2
Author: Felix Schumacher <[email protected]>
AuthorDate: Thu Sep 2 18:41:12 2021 +0200
Add missing documentation about 'Same user on each iteration' for Thread
Groups.
Re-added this bit, as it seems to got lost somehow.
Originally contributed by njkuzas with commit
acdb6482dd3e945e0e8acefd7109b2df3faf505c
Part of #643
Bugzilla Id: 65128
---
xdocs/usermanual/component_reference.xml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/xdocs/usermanual/component_reference.xml
b/xdocs/usermanual/component_reference.xml
index ef8f840..2e014f6 100644
--- a/xdocs/usermanual/component_reference.xml
+++ b/xdocs/usermanual/component_reference.xml
@@ -6563,6 +6563,12 @@ Behaviour can be modified with some properties by
setting in <code>user.properti
<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="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="Delay Thread creation until needed" required="Yes">
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.
