https://bz.apache.org/bugzilla/show_bug.cgi?id=65175
Bug ID: 65175
Summary: Result Status Action Handler when set to 'Continue' is
not overriding the 'Action to be taken after a Sampler
error' in Thread Group
Product: JMeter
Version: 5.4.1
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER 5.4.1
Created attachment 37765
--> https://bz.apache.org/bugzilla/attachment.cgi?id=37765&action=edit
Jmx file that illustrates the issue
Hello, I have an possible bug with the Result Status Action Handler in JMeter
5.4.1.
Test Case
- My Thread Group's 'Action to be taken after a Sampler error' is 'Start Next
Thread Group'. My loop count is 2.
- I have three HTTP Samplers each going to google.com, google.com/xyz (which is
expected to fail with 404), and google.com//services respectively.
- I have a 'Result Status Action Handler' set to Continue that is at the same
level as the HTTP Samplers (ie at the root of the Thread Group).
Expected result:
- Sampler for google.com should pass
- Sampler for google.com/xyz fails but continues
- Sampler for google.com/services should pass
- Loop 1 ends
- Sampler for google.com should pass
- Sampler for google.com/xyz fails but continues
- Sampler for google.com/services should pass
- Loop 2 ends
- Test stops
Actual Result:
- Sampler for google.com should pass
- Sampler for google.com/xyz fails
- Loop 1 ends without executing google.com/services
- Sampler for google.com should pass
- Sampler for google.com/xyz fails
- Loop 2 ends without executing google.com/services
- Test stops
I think the problem may only be with the 'Continue' option in 'Result Status
Action Handler' since every other option seems to stand up under test.
For example, if I have the same test case but set 'Result Status Action
Handler' set to 'Stop Test' the test acts as expected.
- Sampler for google.com should pass
- Sampler for google.com/xyz fails and the test stops
- Loop 2 is not executed
I've attached the jmx file which illustrates the problem.
Thanks,
Mark
--
You are receiving this mail because:
You are the assignee for the bug.
