Displaying Log Output as null when trying to set node value using groovy script
import com.eviware.soapui.support.XmlHolder import com.eviware.soapui.impl.wsdl.testcase.WsdlTestRunContext def request1 = testRunner.testCase.testSuite.testCases["GetEmp"].testSteps["GetEmpDtls"].getPropertyValue("Request") def xml1= new XmlHolder(request1) def getnode1=xml1.getNodeValue("saxon:parse(//tem:GetEmp/tem:InputParameters)//USER_ID") log.info ("GetNodeValue : " +getnode1) def setnode1=xml1.setNodeValue("saxon:parse(//tem:GetEmp/tem:InputParameters)//USER_ID" , "JACK") log.info ("SetNodeValue : " +setnode1) Log Output: Mon Mar 09 16:29:48 IST 2020:INFO:GetNodeValue : test Mon Mar 09 16:29:48 IST 2020:INFO:SetNodeValue : null Expected Logt Output is : SetNodeValue : JACK, BUT Actual Log Output is : SetNodeValue : null I want to set the node value in above scenario, why null value is displaying?, can you provide solution for above senario. In above script emoji icons are displaying, please find the attached script file.
String manipulation in response editor. Response editor usability
I have a slightinconvenience when using response editor. In my project soap response contains tag <result/> wich holds escaped xml response. It's quite a pain every time I use manual testing. First I delete all response containers and then do xml format. I wondering is there some solutions to improve usability of response editor: Is there a way to unescape xml in response editor?Or maybe toggle between CDATA and escaped entities?Or set some setting that changes the length of xml that SoapUI prefers to wrap with CDATA? Do you have string manipulation functions applicable to xml? Do you have some macros feature, so I could automate some actions?
Create an "Response:Outline view" for CDATA
Currently, the OUTLINE view in the Request and Response only apply to well formed data. Defined by the WSDL or WADL. In cases where the service has taken advantage of the CDATA feature to hide the implementation of the service from the WSDL/WADL. It would be nice to be able to view the CDATA in a separate tab (just like Outline), and be able to make assertions based on that CDATA outline view. Currently it is required to do Scripting to expose the CDATA in the same way a well structured WSDL response is viewed.