# Not able to validate SOAP call response **URL:** \ **Category:** API Testing\ **Tags:** api-testing, katalon-studio\ **Created:** [September 15, 2021, 8:26pm UTC](https://forum.katalon.com/t/not-able-to-validate-soap-call-response/58330 "2021-09-15T20:26:53Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![kazurayam](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/kazurayam/32/333_2.png) [@kazurayam](https://forum.katalon.com/u/kazurayam)\ **Post date:** [September 16, 2021, 7:51am UTC](https://forum.katalon.com/t/not-able-to-validate-soap-call-response/58330/7 "2021-09-16T07:51:13Z")
@milad.abbasi Your XML response contains `env:Header` element with content elements. ```auto 2021-09-15T19:23:13.688Z 2021-09-15T19:28:13.688Z ... ``` The `` element makes `WS.verifyElementText` keyword confused. _Surprisingly enough, it expects the SOAP response to have `` only_. Let me be precise. See [https://github.com/katalon-studio/katalon-studio-testing-framework/blob/master/Include/scripts/groovy/com/kms/katalon/core/testobject/ResponseObject.java](https://github.com/katalon-studio/katalon-studio-testing-framework/blob/master/Include/scripts/groovy/com/kms/katalon/core/testobject/ResponseObject.java), Line #77: ```auto Node node = (Node) xPath.evaluate("//*//*//*", doc, XPathConstants.NODE); ``` This is where the problem comes from. When the response XML contains no `` element, the `node` variable will be ```auto .... ``` which is as you exepect. But when the response XML contains a `` element, the `node` variable will be ```auto ... ``` which is not what you expected. Here you would get an error: ```auto ? Expected text is 'Approved' but actual element text is: ``` I am sure that the Katalon programer who wrote `WS.verifyElementText` keyword ignored a case where a SOAP response has a `` element. c/c @duyluong When I made a search in this forum with keyword “WS.verifyElementText”, I found quite a lot of questions. People claimed that they can not get the expected value of XML nodes via this keyword. - [How to verify REST XML Response? - #11 by Niranjan](http://forum.katalon.com/t/how-to-verify-rest-xml-response/21353/11) @Brian_Ducson - [Verify element in response, strange behaviour](http://forum.katalon.com/t/verify-element-in-response-strange-behaviour/14168) @Paul_Reijling - [SOAP call has unbound prefix fault - #5 by jjbarser](http://forum.katalon.com/t/soap-call-has-unbound-prefix-fault/8283/5) @Zarashima - [How to create VerifyElementText Test Case for MTOM Enabled SOAP Web Services? - #6 by Zarashima](http://forum.katalon.com/t/how-to-create-verifyelementtext-test-case-for-mtom-enabled-soap-web-services/6166/6) @Zarashima - [Katalon SOAPUI Validating Response](http://forum.katalon.com/t/katalon-soapui-validating-response/45352) @huynguyen These questions are unresolved, outstanding. I am afraid that nobody has ever realised how bad the line #77 of [https://github.com/katalon-studio/katalon-studio-testing-framework/blob/master/Include/scripts/groovy/com/kms/katalon/core/testobject/ResponseObject.java](https://github.com/katalon-studio/katalon-studio-testing-framework/blob/master/Include/scripts/groovy/com/kms/katalon/core/testobject/ResponseObject.java) is. It will continue confusing people in future. Also, I would argue that the keyword name `WS.verifyElementText()` is inappropriate. This name does not express what it does actually. I would propose to Katalon Team 1. it should be separated into 2 keywords: one for JSON response (e.g, `WS.verifyJsonElementText()`), another for SOAP response. 2. the keyword for SOAP response should be named “WS.verifySOAPBodyElementText()”, and clearly state that it works only with a SOAP response without a `Header` element. 3. also the documentation should clearly state that `WS.verifySOAPBodyElementText()` does not work for arbitrary XML responses like `AB`. As for JSON response, `WS.verifyElementText` might be OK. But for XML response, this keyword does not help. You shouldn’t use it. If Katalon Team finds it difficult to change the codebase for the backward-compatibility concern, then, I would suggest, **you should improve the [documentation](https://docs.katalon.com/katalon-studio/docs/ws-verify-element-text.html)** so that people do not waste their time. * * * @milad.abbasi What else can you do? You should avoid the builtin `WS.verifyElementText` keyword as long as your XML contains `` element. In Katalon Studio, you can get access to the XML response body, parse it and extract text content out of the XML elements; then you can make assertions: do these by your Groovy scripts (Test Case and Custom Keywords) By the way, I looked at other API Testing tool Postman. I found that you have to write a bunch of custom codes (in Node.js) to process and verify SOAP messages in Postman. Now a question to you would be; which tool (which scripting language) you like? * * * Here is a sample Test Case script that can verify your XML Response. ```auto import static com.kms.katalon.core.testobject.ObjectRepository.findTestObject import com.kms.katalon.core.testobject.RequestObject import com.kms.katalon.core.testobject.ResponseObject import com.kms.katalon.core.webservice.keyword.WSBuiltInKeywords as WS import groovy.util.slurpersupport.GPathResult ResponseObject response = WS.sendRequest((RequestObject)findTestObject('data')) println "response.getResponseText() : " + response.getResponseText() GPathResult envelope = new XmlSlurper().parseText(response.getResponseText()) .declareNamespace(env: "http://schemas.xmlsoap.org/soap/envelope/", wsse: "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd", wsu: "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd", ns: "beep", ns2: "bop", ns1: "foo") assert envelope.'env:Header'.'wsse:Security'.'wsu:Timestamp'.'wsu:Created'.text().contains('2021-09-15T19:23:13.688Z') assert envelope.'env:Body'.'ns:PreAuthorizeResponse'.'ns:Receipt'.'ns1:TransactionResult'.text().contains('Approved') ``` * * * The following post shows you an alternative approach to verify XML respose using XPath. > [@Web Service tests - REST API - XML Response : Problem with verification / getResponseBodyContent does not contain all of the response's body](http://forum.katalon.com/t/web-service-tests-rest-api-xml-response-problem-with-verification-getresponsebodycontent-does-not-contain-all-of-the-responses-body/58016/12): > > You showed an XML like this: The text “A2” is followed by a new line character. It is 0x41 0x32 0x0D 0x0A in hex-decimal representation. If it is really the case, your Custom Keyword had better to “normalize” whitespaces in the XML content text before testing equality to the text you expect; like this (original) return res && BuiltinKeywords.verifyEqual( getXmlNodeText(responseText, locator), text, flowControl) (proposed) return … I think that a Test Case that uses XPath is the best approach to verify a SOAP message. --- _[View the full topic](https://forum.katalon.com/t/not-able-to-validate-soap-call-response/58330)._