DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20997>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20997 Different behaviour of Response Assertion Summary: Different behaviour of Response Assertion Product: JMeter Version: 1.9.RC2 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: Other Component: Main AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If a Response Assertion detects that the sample has already failed, it creates a new AssertionResult and sets the failure message to the contents of the responseData field. This is not done by any of the other Assertions, which always check the sample against the Assertion conditions. The current behaviour of Response Assertion does not seem correct - surely if there are several Assertions related to a sample, all of them should be checked? Or none of them. And why set the failure message to the contents of the response data? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
