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.
comparing two xml response
hi i am shifting my svc service to different platform and i would like to test both services the original and the new one with same request and compare the response. the response is not 100% identical i have element with execution time that i need to ignore. also the response contain UTF-8 Characters, any suggestions for simple solution?
Comparing file from stores to output file locks both files sometimes
Hi, I have around 300 test cases for a desktop application, each has a saved expected result file in the Files stores. Each test case works as follows : Generates a data table. Export the data table to a file. Then : Files.stored_file.check("D:\thing\output_file.txt"); so the first time, the file gets exported and saved and compared succesfully, now if you re-run the test case ,, sometimes it works, and sometimes not! no specific steps to reproduce! Reason is that the output file gets locked, and won't get deleted/overwritten unless test complete is closed. if you reopen test complete it works very well. can you please help me with this? Thanks.
