jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 62941] New: Transaction Controller : ORed aggregation of statuses, to ease "Retry request N times on fail" test implementation
Date Thu, 22 Nov 2018 16:24:16 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=62941

            Bug ID: 62941
           Summary: Transaction Controller : ORed aggregation of statuses,
                    to ease "Retry request N times on fail" test
                    implementation
           Product: JMeter
           Version: 5.0
          Hardware: PC
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: avam0nst3r@gmail.com
  Target Milestone: JMETER_5.0

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
Mime
View raw message