Summary: | Response Assertion "Ignore Status" cancels preceding assertion failures. | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | deane.sloan |
Component: | HTTP | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | trivial | ||
Priority: | P5 | ||
Version: | 2.1.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP |
Description
deane.sloan
2006-03-02 01:49:00 UTC
This is behaving as designed. The documentation states: "When the Ignore Status checkbox is selected, the Response status is forced to successful before evaluating the Assertion." The purpose of the checkbox is to allow the response status to be checked, even if the request has failed, e.g. it allows one to check for a 404. Thanks - Probably led astray a bit by the doco statement "There is no difference between setting up one Assertion with multiple patterns and setting up multiple Assertions with one pattern each (assuming the other options are the same). " - the statement seems to be incorrect based on your response and observations. My bad - created a contrived example presuming the issue was a bug rather than a doco thing. Simply put - splitting a check where you want to make your own determination about HTTP 400+/500+ responses into multiple response assertions using "Ignore Status" won't reliably work - the patterns need to be in the one response assertion. The documentation around response assertion has a statement that would lead you to believe otherwise ("There is no difference between..."). Just a minor doco thing - but still has the same impact if you made the choice to split your assertion up based on the statement... BTW - this seemed like a viable approach to let a known HTTP 500 error through for a period of time by trapping everything but... Thanks for taking the time to read this. (In reply to comment #2) > Thanks - > Probably led astray a bit by the doco statement "There is no difference between > setting up one Assertion with multiple patterns and setting up multiple > Assertions with one pattern each (assuming the other options are the same). " - > the statement seems to be incorrect based on your response and observations. Your example did not use the same options... I'll see about improving the documentation for the check-box. Documentation has been updated. Ignore Status should only be used on the first Assertion This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1694 |