Compare test step
Purpose The process of testing often requires to compare test results to expected values. When we need to check a specific value, we can use assertions. However, there are often occasions when we need to compare one documents to another (e.g. XML, JSON). I propose to introduce a new type of test step: Compare test step. Functionality Compare test step would allow: Select documents: users would select source and target document from test step requests, responses, properties and other document holders in SoapUI environment, similarly as the Property Transfer test step does. Type of comparisson: the user could choose whether the documents have to be identical (both structure and values) or similar (only the structure should be same). Also the user could choose to ignore differences in whitespaces, attributes, or namespaces, or even data types which to ignore (e.g. xsd:dateTime is typically different). List of items to compare/ignore: the user could list the items which should be ignored, represented by XPath statements. Also there would be an opposite option: a list of XPath statements to check and to ignore the rest of the documents. Suggestions The Compare test step can utilize the XMLUnit library for XML and thus expose its function via SoapUI user interface. The Compare step can be similarly used for JSON documents.9KViews8likes3CommentsExcel datasink to consume repeating xml elements without having to map multiple properties
Currently there's no functionality that provides the abiltiy to map an XML rest response with repeating elements to a datasink without mapping each indivitual repeating element. Example:https://community.smartbear.com/t5/SoapUI-Pro/How-to-map-repeating-elements-from-xml-response-to-datasink/m-p/199559#M45747 Is there a way to map a repeating element from a response into a datasink automatically, rather than having to click getData and manually clicking each one. So, if I have 25 repeating elements. Widgets again. They all have the same attributes. A1, A2, A3. I want my sink to collect each of the attributes from each of the widgets, but I don't want to have to map it explicitly in the data sink property and the every one of the 25 widgets (x3 attributes) in my response. example: <widgets> <widget> <att1>abc</att1> <att2>xyz</att2> <att3>asd</att3> </widget> <widget> <att1>abc</att1> <att2>xyz</att2> <att3>asd</att3> </widget> ... </widgets> In my datasink, I'd like to map these out 1 element to 1 row in excel: excel row 1 (first widget): att1: abc,att2: xyz,att1: asd excel row 2 (second widget): att2: abc,att2: xyz,att1: asd What I'm trying to avoid is this: All the way through dozens of these objects.1.6KViews2likes1CommentSOAP UI Return XML Dumping with Invalid Characters
Introduction:Hello Community! I hope I am posting in the correct place. Precursory Information:I am currently using SOAP UI Free to attempt to validate a WSDL. I have a service that looks like this: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header> </SOAP-ENV:Header> <SOAP-ENV:Body> ...SOAP BODY HERE... </SOAP-ENV:Body> </SOAP-ENV:Envelope> This sends out ok, and I get a return message. Precursory Explination: The way myreturn code is designed is to send a response with an XMLattached. I've done research on Request/Reponsewith attachment's in SOAP UI, and it looks like it can do it. I've read the documentation on attachment's, and done additional research on SOAP UI but I cannot find my exact issue. Issue: When returning the XML, I am recieving a bunch of invalid characters, along with a 'dump' of the attached xml. It looks like: ) ) [Invalid Character Here]uuid:XXXXXXX-YYYY-ZZZZ-AAAA-123456789123 <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body/></soapenv:Envelope> [Invalid Character Here]XXXXXXYYYYYYYYYZZZZZZZZZZ11111112222222233333333333/xml ...CORRECT XML THAT IS SUPPOSED TO BE ATTACHED HERE... Note: I am not sure how much I am allowed to share of the code/digits - but the ...CORRECT... is a correct XML I am expecting, and the XYZA and 1234... are all characters that change every time. Is there a way to prepare SOAP UI for this attached XML and not get this dump? I won't be able to validate this the way it is. What I have tried: I have tried adjusting all of the settings in the Request Properties windows with no luck. Has anyone experienced this? Could someone help me prepare my SOAP UI for the attached XML, rather than dump different characters and the contents? Thanks in advance!Solved3.8KViews1like3Comments