| Summary: | If Controller does not work properly when Transaction Controller generates parent sample | ||
|---|---|---|---|
| Product: | JMeter - Now in Github | Reporter: | onlinehenk |
| Component: | Main | Assignee: | JMeter issues mailing list <issues> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | p.mouawad |
| Priority: | P2 | ||
| Version: | 2.13 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | JMeter testplan with example of the bug and example of the workaround. | ||
*** This bug has been marked as a duplicate of bug 59067 *** This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/3823 |
Created attachment 33535 [details] JMeter testplan with example of the bug and example of the workaround. When you want to use the If Controller when your variable == 'something', this does not work after 'Start next Thread loop'. Situation: ${VariableForIf} = IfIsYes If controller condition: "${VariableForIf}" == "IfIsYes" In the If controller there is a assertion: When "${VariableForIf}" == "IfIsYes" the assertion will fail. Then 'Start next thread loop' is applicable. Second time the If controller is not touched. Expected situation: As long as ${VariableForIf}" == "IfIsYes" the flow is going into the If controller, the assertion will fail, and again and again. Work arround: check out 'generate parent sample' of the Transaction Controller. See attachment for an example.