Bug 43364 - changed behaviour of ifcontroller in version 2.3?
changed behaviour of ifcontroller in version 2.3?
Status: RESOLVED FIXED
Product: JMeter
Classification: Unclassified
Component: Main
2.3
Other other
: P2 enhancement (vote)
: ---
Assigned To: JMeter issues mailing list
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2007-09-12 07:33 UTC by Christoph
Modified: 2007-09-19 15:44 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph 2007-09-12 07:33:13 UTC
hi,
i just noticed that the behaviour of the if-controller changed from version 2.2 
to 2.3.
the condition is now only evaluated for the first time. in jmeter 2.2, this 
condition was evaluated for all samples within the if-controller.
if found that this behaviour was practically... i think it would be great if 
the if-controller would have an option "evaluate for all children" were one can 
enable the old behavior of the if-controller.

greets,
  chris
Comment 1 Sebb 2007-09-12 10:22:32 UTC
Yes, the behaviour was fixed in Bug 41612.

But it should be possible to add an option to enable the original behaviour.
Comment 2 Sebb 2007-09-19 15:12:48 UTC
Added to SVN (rel-2.2) in 0
Comment 3 Sebb 2007-09-19 15:44:11 UTC
Copied to trunk in SVN 0