Reputation: 12447
You create and test your script locally in jmeter, so that later you can upload it to blazemeter to run.
The test contains hundreds of transaction controllers, each representing a page, and created by the script recorder.
The problem is, to run it locally, and get transaction controller summary by page, not by every request, you have to check "generate parent sample".
but this has to be disabled when you upload to blaze.
How do people handle this?
It doesn't seem possible to bulk edit these or use a variable, every transaction controller (representing a page) has to be manually edited every time.
Any suggestions?
Upvotes: 0
Views: 706
Reputation: 168147
JMeter .jmx scripts are basically XML files so you can open your script with text/XML editor of your choice, look for the next line:
<boolProp name="TransactionController.parent">false</boolProp>
it means that the Transaction Controller doesn't generate the parent sample. If you replace it with:
<boolProp name="TransactionController.parent">true</boolProp>
it will generate the parent sample (and vice versa)
You can use Taurus tool which has capability of bulk changing arbitrary JMeter test element property to the desired value, in your case disabling "parent" mode of the Transaction Controller would be something like:
execution:
scenario:
script: test.jmx
modifications:
set-prop:
"Transaction Controller>TransactionController.parent": false
Upvotes: 1