Summary: | Transaction Controller in "Generate Parent Sample" mode : Assertion fails while is should not | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | shmulikk |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | REOPENED --- | ||
Severity: | normal | CC: | p.mouawad, shmulikk |
Priority: | P2 | ||
Version: | 2.9 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Attachments: | Testplan to reproduce the issue |
Description
shmulikk
2013-01-24 21:02:52 UTC
Created attachment 29893 [details]
Testplan to reproduce the issue
The transaction controller haven't response data, thus Response Assertion can't check in this data. In Response Assertion, you can change option "Apply to:" Sub-samples only to work. I am not sure it is invalid. In more complex cases, I have both Transaction Controllers and (HTTP) Samplers (which are not in Transaction Controllers) in the same level in a thread group. The solution you suggested will not work in such cases. Perhaps we need to disable assertion test on Transaction controller when a Assertion Response passes inside. Thus, when we have some TC and HTTP Requests at same level than a Assertion Response with Apply to "Main and Subsamplers" there haven't errors (null data on tc) (and if no errors on req http) There is something odd happening here. If the TC is set to not generate a parent sample, then the RA works. Adding an Assertion Results Listener shows two entries. The RA should fail when applied to the TC sample result as that is empty. Hoewever it does not fail; looks like the RA somehow runs against the wrong data here. Yet the AR Listener shows TC in its list. This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/3047 |