https://bz.apache.org/bugzilla/show_bug.cgi?id=64093
Bug ID: 64093
Summary: Threadgroups run with outdated parameters after
updating them via PreProcessor
Product: JMeter
Version: 5.2.1
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_6.0.0
Created attachment 36977
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36977&action=edit
Example Testplan to verify the bug
I encountered the following issue while working with JMeter:
If parameters of a ThreadGroup are changed in a preprocessor, e.g. Num of
Threads, Loop Count or Duration, then the ThreadGroup is ran with the values
present BEFORE changing them in a ThreadGroup. The following setup can be used
to reproduce:
Testplan
* JSR223 Preprocessor (Groovy)
* props.setProperty("threads", "1")
* Summary Group
* Thread Group(Number of threads: ${__P(threads,10)} )
* JSR223 PreProcessor (Groovy)
* log.info("==========================A THREAD WAS RUN")
* Property Display
Following need to be taken to reproduce the issue:
1) Create the setup
2) Close and Re-Open JMeter
3) Open Testplan
4) Verify that threads is not present in PropertyDisplay
5) Execute Testplan
6) Verify that Summary Report shows 10 Samples, Output is seen in log
7) Re-Run the Testplan
8) Verify that Summary Report now shows 11 Samples, Output is seen in log
I could neither find this behaviour documented nor find a proper workaround for
it, so I assume this is unintended behavior.
--
You are receiving this mail because:
You are the assignee for the bug.
