Bug 62941 - Transaction Controller : OR aggregation of statuses, to ease "Retry request N times on fail" test implementation
Summary: Transaction Controller : OR aggregation of statuses, to ease "Retry request N...
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.0
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: JMETER_5.0
Assignee: JMeter issues mailing list
Depends on:
Reported: 2018-11-22 16:24 UTC by avam0nst3r
Modified: 2019-03-07 20:24 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description avam0nst3r 2018-11-22 16:24:16 UTC
Transaction Controller enhancement - make user specify transaction status aggregation rules from child sampler's statuses. 

Currently transaction is successful when ALL child samplers are successful. (AND rule) 

I suggest to add the "OR aggregation" checkbox to Transaction Controller UI, meaning that transaction is successful when there is at least one successful child sampler. 
This checkbox should be unchecked by default.

This will help to implement the "http retry" much easier that it is possible today.
Check this Frankenstein for example (not working in Jmeter5 btw): https://www.blazemeter.com/blog/how-to-count-retries-as-a-single-request-in-jmeter

What I'm trying to achieve, is having these "OR-aggregated" transactions in Jmeter reports as successful, when a sequence of failed child samplers requests ended up with successful one. With transaction time still being the total of all child samplers time, as it is now. And I still want to have proper success/fail statuses for child samplers within the transaction.
Comment 1 The ASF infrastructure team 2022-09-24 20:38:15 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4930