Forum Discussion
SmartBear_Suppo
Alumni
13 years agoHi,
I'm not seeing this behavior for xpath assertion and junit reports. The entire assertion and reason for failure is being shown.
[XPath Match] XPathContains assertion failed for path [declare namespace sam='http://www.soapui.org/sample/';
//sam:searchResponse[1]/item[3]/description[1]] : NullPointerException:null
Test Request: Buy Failed
[XPath Match] XPathContains comparison failed, expecting [You should already have it.], actual was [?]
[XPath Match] XPathContains comparison failed, expecting [Item 5], actual was [?]
[XPath Match] XPathContains comparison failed, expecting [1 license], actual was [?]
I don't think there is any character limit on the assertion length in the report, where is it cutting off at in the report?
Also what version of SoapUI Pro are you using?
Regards,
Marcus
SmartBear Support
I'm not seeing this behavior for xpath assertion and junit reports. The entire assertion and reason for failure is being shown.
[XPath Match] XPathContains assertion failed for path [declare namespace sam='http://www.soapui.org/sample/';
//sam:searchResponse[1]/item[3]/description[1]] : NullPointerException:null
Test Request: Buy Failed
[XPath Match] XPathContains comparison failed, expecting [You should already have it.], actual was [?]
[XPath Match] XPathContains comparison failed, expecting [Item 5], actual was [?]
[XPath Match] XPathContains comparison failed, expecting [1 license], actual was [?]
I don't think there is any character limit on the assertion length in the report, where is it cutting off at in the report?
Also what version of SoapUI Pro are you using?
Regards,
Marcus
SmartBear Support