[Res] JUnitReport How to Show Xpath Assertion

Hi,

Are you doing any kind of customization in your JUnitReport? Such as using a custom class?


Regards,
Marcus
SmartBear Support

No. I am not doing any Customization Report.

Hi,

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 am adding Assertions dynamically by reading the assertions from File as below in the TestRunListener.beforeStep.

Could you please verify if there is anything wrong on the below code?

Do I have to set any parameter to print the complete assertion in the junit report?

I am running the project from maven.

/*
* Create Assertion
*/
def buildAssertion(row, testStep, testCase){
log.info("\n Xpath Assertion, Row Number :"+ row.getRowNum())
def xpath = row.getCell(0)
def xpathValue = row.getCell(1)
def xpathValidationType = row.getCell(2)

//Print the Row Values
log.info("XPATH :"+row.getCell(0))
log.info("XPATH_VALUE :"+row.getCell(1))
log.info("XPATH_VALIDATION_TYPE :"+row.getCell(2))

def assertionName = testCase.name + "_" + testStep.getLabel() +"_Assertion_" + row.getRowNum()
def assertion = testStep.addAssertion("XPath Match")
log.info("%%%%%%%%%%%%%%%%%%%%%%%%%%%%% "+assertion)
assertion.name= assertionName
assertion.setIgnoreNamespaceDifferences(true)

if(xpathValidationType.getStringCellValue() == "1"){
assertion.path = "exists("+xpath.getStringCellValue()+")"
assertion.expectedContent = "true"

log.info("Added Xpath Existance Assertion :"+xpath + " to TestStep " + testStep.getLabel())
} else if (xpathValidationType.getStringCellValue() == "2"){
assertion.path = xpath.getStringCellValue()
assertion.expectedContent = xpathValue.getStringCellValue()
log.info("Added XPath Match Assertion :"+xpath + " to TestStep " + testStep.getLabel())
} else if (xpathValidationType.getStringCellValue() == "0"){
log.info("XPATH_VALIDATION_TYPE =" +xpathValidationType +".Hence Not Adding Assertion.")
}
}

I am using SOAP UI Version 4.6.2.

I don't think it is cutting. it is just not printing the xpath assertion instead if I have an assertion for an element or attribute it just prints that only instead of printing the whole assertion.

I tried this in UI as well and the result is same.

Hi,

As an FYI we do not support custom code solutions. Also you are running in maven which is a 3rd party tool which we do not support.

Are you able to post a screen shot of what your seeing in the UI so can I better understand the problem?
Have also double checked the file that you are reading to get the assertions that it contains the entire string you expect?



Regards,
Marcus
SmartBear Support

Marcus, Thanks for your reply.

I do not think this is a Third Party Tool Issue.(I might be wrong)

I also tried this by adding an Xpath Assertion in SoapUI. I created a project and have a HttpRequest as TestStep.

Please see the attached screenshot.

Thanks for looking into this and appreciate all the help.

Hi,

I'm going to ask the development team about this. I haven't been able to get a custom error message for the XPath assertion in Groovy. I did create enhancement request SOAP-1155 since you and another pro user have requested this.



Regards,
Marcus
SmartBear Support

Thanks for the time and help.

Hi,
Unfortunately SoapUI doesn't include the path specified in the assertion when the comparison fails (i.e. the value is found for the path but doesn't match), it includes the path in other error messages though, and there is no work around to fix this.
We have discussed it with product owner and he has approved it (SOAP-1155) to be fixed in next minor release.

Thanks for reporting this.

Best Regards,
Prakaksh