DO NOT REPLY [Bug 26371] New: - TestFailed message missing 'not'

[bu...@apache.org]

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=26371>.
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=26371

TestFailed message missing 'not'

           Summary: TestFailed message missing 'not'
           Product: JMeter
           Version: 1.9.1
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: heinz.vanpee@gmx.de


If you use a ResponseAssertion and use the not checkbox the
TestFailed message still says 'expected to contain ...' instead of 'expected 
not to contain ...'.
I tracked this down to a missing clone method.
Somewhere the AbstractTestElements are cloned via the clone() Method of 
AbstractTestElement. As ResponseAssertion has no clone method the private 
fields notMessage and failMessage are not copied in the new Object.

I fixed that on my local installation with adding a clone method to 
ResponseAssertion:

    public Object clone() {
        ResponseAssertion raClone = (ResponseAssertion) super.clone();
        raClone.notMessage = notMessage;
        raClone.failMessage = failMessage;
        return raClone;  
    }

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org